Re:A Proposal for Package Versioning in Go
by randomdata on Monday March 26, 2018 @05:22PM
(#16682736)
> 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.
Re:A Proposal for Package Versioning in Go
by kasey_junk on Monday March 26, 2018 @09:53PM
(#16684482)
What is it?
go get.
Re:A Proposal for Package Versioning in Go
by kasey_junk on Monday March 26, 2018 @10:48PM
(#16684778)
Does that finally work with private repos?
Re:A Proposal for Package Versioning in Go
by sethammons on Tuesday March 27, 2018 @07:30AM
(#16687277)
It 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.
Re:A Proposal for Package Versioning in Go
by kasey_junk on Tuesday March 27, 2018 @09:19AM
(#16687995)
So having to reset my git config, either globally impacting everything I do, or manually for every project I use go get in...
Got it.
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.