News for hackers. Stuff that matters.

A comment on Go += Package Versioning. Parent comment

Re:Go += Package Versioning by shkkmo on Tuesday February 20, 2018 @03:30PM (#16423892)
Just because you don't need reproducible builds doesn't mean nobody needs them.

As soon as some tool is used to provide reproducible builds, you have effective version pinning.

If your organization values avoiding technical debt accumulation over reproducable builds, they don't don't have to use version pinning and can always run 'go get' with the '-u' flag.

> once package users are using version pinning, it's easier for package maintainers to make changes that aren't backwards compatible.

I don't think ease of making backwards incompatible changes with vgo. Both before and after vgo, backwards incompatible changes must go in a new major version / new import path. The ability to pin major versions already exists.

[ Parent | on HN ]
Re:Go += Package Versioning by 0xdeadbeefbabe on Tuesday February 20, 2018 @05:00PM (#16424634)
Although no one talks about it you don't have to use go get. I don't know if that's bad or not, but at least two projects are doing it.
[ Parent | on HN ]