[sfrailsdev]

vendor directories are no longer optional, which is nice.

Go get now update submodules... I'm honestly not sure what the current hack is for package management, but I assume people are still doing wrappers around go get to pin to commits/versions, (or else building your own repos for funsies), and I'm wondering if that breaks anything.

[nathany]

There are active discussions on the Go Package Management mailing list and the intention to propose further improvements to the go toolchain for future releases. We had good discussions with the Go Team during GopherCon last month.

https://groups.google.com/forum/#!forum/go-package-managemen...

[owaislone]

Hopefully we'll have something official soon. For now, glide has been working well for us.

[Cidan]

To be clear, vendor directories are still optional to use, you just don't have to enable them by default.

We use a unirepo for all of our Go work, and being forced to use the vendor directory would be a massive headache.

[sfrailsdev]

My understanding is that there is no longer an option to disable them as a feature as there was in 1.6, though of course you don't have to use them.

[nathany]

Yup, and you can always rename vendor/ to _vendor/ if you want to ignore them temporarily.