News for hackers. Stuff that matters.

A comment on A response about dep and vgo. Parent comment

Re:A response about dep and vgo by pcwalton on Saturday July 28, 2018 @02:12AM (#17631836)
> It's not like vgo makes it hard to upgrade all dependencies to their most recent version - it's done automatically with a single command, if you want it.

And how does it guarantee that this actually results in anything that works, if upper bounds are not supported?

[ Parent | on HN ]
Re:A response about dep and vgo by kaeshiwaza on Saturday July 28, 2018 @03:38AM (#17632099)
Upper bound are major version, everything between should be api compatible (it's in the specs of go modules).
[ Parent | on HN ]
Re:A response about dep and vgo by pcwalton on Saturday July 28, 2018 @01:35PM (#17634108)
Except for version 0.x, and with vgo you have no recourse if somebody didn't follow the rules and made an incompatible change.
[ Parent | on HN ]
Re:A response about dep and vgo by jessaustin on Sunday July 29, 2018 @09:49AM (#17638109)
This is the whole point: just specify the version before the change, and it won't bother you.
[ Parent | on HN ]
Re:A response about dep and vgo by pcwalton on Monday July 30, 2018 @01:21AM (#17642240)
Until someone actually wants to update their dependencies, writes "go get -u", and breaks the build.
[ Parent | on HN ]
Re:A response about dep and vgo by jessaustin on Monday July 30, 2018 @04:15PM (#17647601)
Well sure, you probably want to test after updating all of those dependencies. That's a good reason to only update when necessary. Do you argue that some other scheme prevents bugs in dependencies? That hasn't been my experience...
[ Parent | on HN ]