govendor

The constant thrash caused by the lack of a standard package management tool—even a de facto standard. Just look at the various package managers that have come and gone over the years: 1. https://github.com/tools/godep 2. https://github.com/kardianos/govendor 3. https://github.com/robfig/glock 4. https://github.com/rogpeppe/govers 5. https://github.com/Masterminds/glide 6. https://github.com/golang/dep I'm sure I'm forgetting a few. And just when it seemed the Go team might be ready to standardize around Dep (6), they threw this wrench in the works. I'm of two minds about vgo. I think it has some interesting ideas, but Dep works today, is widely adopted, and has nearly all the features you'd expect from a modern package manager.

Check out the `dep` tool: https://github.com/golang/dep It is the future of official vendoring tools. You could also look at `govendor`: https://github.com/kardianos/govendor I've used govendor in some projects and found it agreeable. Best of luck :-)

> What's the reason for yet another utility? > Some copy the source code of dependencies into the vendor directory: I don't agree with any of the stated problems there. Unless you are building a library you should commit your dependencies and not rely on third party repos being available. I can't stress enough how useful govendor [1] is if you do Go professionally. [1] https://github.com/kardianos/govendor

There are multiple ways to do this. Personally, I've used and liked govendor https://github.com/kardianos/govendor. As of go 1.5, its supported by the language itself: https://github.com/golang/go/wiki/PackageManagementTools

> Godep works differently than the endorsed approach… > Instead of requiring changes to be made to the source > code to support the vendored import path, the GOPATH is > modified to use the vendored folder. This isn't correct — Godep has two modes, and this is just one of them. The other way is indeed rewriting import paths. This is incorrect on another level, too. Rewriting import paths isn't "endorsed" by the Go authors. In fact, Russ Cox, in his GopherCon 2015 keynote, explicitly noted that > Our basic proposal was that all tools agree on the > approach of rewriting import paths during vendoring... > > [But] the community spoke with essentially one voice to > say that rewriting import paths during vendoring was not > tenable... > > Keith Rarick posted an alternate proposal for a minim