4 ms·
> Go doesn't "do" that Literally the first example of the Go tour [1] tells you to run "go get". "dep" is not (yet) an official part of Go's tooling. So when t
by calcifer 9y ago
> Go doesn't "do" that
Literally the first example of the Go tour [1] tells you to run "go get". "dep" is not (yet) an official part of Go's tooling. So when the only official tool fetches HEAD and calls it a day, I think it's perfectly fine to say "Go does that".
[1] https://golang.org/doc/ https://golang.org/doc/
- petre 9y agoIt's pretty annoying. Most of the time I want to build a stable version not HEAD which could break in many ways. Using HEAD as a dep is pretty much insane. Stop publishing for several months and the code would most likely fail to build.
- slrz 9y agoThe 'go get' tool is just a small convenience wrapper around git/hg/svn. Its intended for use by developers, for quickly taking a look at some source code. The tour use case you cited is also a good fit for 'go get'. It was never intended to be a part of your production build process. If you push its outputs directly to production, you're holding it wrong.