Godep: Dependency Management in Go(blog.codeship.com)
blog.codeship.com
Godep: Dependency Management in Go
https://blog.codeship.com/godep-dependency-management-in-golang/
1 comments
Thanks for the feedback! We're certainly excited about the recent move towards go's experimental vendoring, I can't say I've had many positive experiences with vendoring myself as it is. The only thing worse than vendoring is not vendoring.
This article is a little outdated in terms of the maintainers endorsements, I'll see if we can update it with that, along with the correction.
This article is a little outdated in terms of the maintainers endorsements, I'll see if we can update it with that, along with the correction.
'gb' seems promising but getting it to work with existing code editors is a bit of a pain point.
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
Dependency management in Go is an ongoing sore spot, but there's light at the end of the tunnel, in the form of the referenced proposal[0], its spec[1], and the third-party tool gb[2]. Godep was a good intermediate solution, but it should no longer be recommended as something worth exploring.
[0] https://blog.golang.org/open-source
[1] https://github.com/kardianos/govendor
[2] http://getgb.io