Go vgo: Semantic Versioning and Human Error

Re:Go vgo: Semantic Versioning and Human Error by dbaupp on Monday May 21, 2018 @10:14PM (#17123309)

Many package managers interpret semver in a similarly mechanical way, e.g. npm, bundler, cargo (and, I think, elm-package, and I'm sure others too), but they choose different versions based on that information.

[ Parent | on HN ]

Re:Go vgo: Semantic Versioning and Human Error by mzl on Tuesday May 22, 2018 @02:16AM (#17124047)

And crucially, in these systems you are given an escape hatch (declaring versions that are not ok), which vgo does not support.

[ Parent | on HN ]

Re:Go vgo: Semantic Versioning and Human Error by hectormalot on Tuesday May 22, 2018 @06:15AM (#17124880)

I think vgo allows you exclude specific versions in go.mod. It only works for specific versions, not ranges though

[ Parent | on HN ]

Re:Go vgo: Semantic Versioning and Human Error by mzl on Tuesday May 22, 2018 @07:14AM (#17125093)

There are exclusions, but they are only available for the current module:

> Exclusions only apply to builds of the current module. If the current module were required by a larger build, the exclusions would not apply.

https://research.swtch.com/vgo-tour

[ Parent | on HN ]