3 ms·
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
by benesch 9y ago
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 https://github.com/tools/godep
2. https://github.com/kardianos/govendor https://github.com/kardianos/govendor
3. https://github.com/robfig/glock https://github.com/robfig/glock
4. https://github.com/rogpeppe/govers https://github.com/rogpeppe/govers
5. https://github.com/Masterminds/glide https://github.com/Masterminds/glide
6. https://github.com/golang/dep 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.
- randomdata 9y ago> The constant thrash caused by the lack of a standard package management tool There is a standard, and has been one from the early days. The catch is that the standard is not loved by all, so others have created competing package management systems to fit their own needs.
- kasey_junk 9y agoWhat is it?
- lox 9y agogo get.
- kasey_junk 9y agoDoes that finally work with private repos?
- sethammons 9y agoIt always has. You have to edit your gitconfig. On mobile, so I can't paste mine. A Google search should get you there. It did for me like 5 years ago.
- kasey_junk 9y agoSo having to reset my git config, either globally impacting everything I do, or manually for every project I use go get in... Got it.