News for hackers. Stuff that matters.

A comment on A Proposal for Package Versioning in Go. Parent comment

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.

[ Parent | on HN ]
Re:A Proposal for Package Versioning in Go by kasey_junk on Monday March 26, 2018 @09:53PM (#16684482)
What is it?
[ Parent | on HN ]
Re:A Proposal for Package Versioning in Go by lox on Monday March 26, 2018 @10:37PM (#16684705)
go get.
[ Parent | on HN ]
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?
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.

[ Parent | on HN ]