News for hackers. Stuff that matters.
Re:Go and Versioning: Minimal Version Selection by uluyol on Wednesday February 21, 2018 @09:03PM (#16434633)
I don't see why hashing is incompatible with the minimum version algorithm. As far as I can tell, the algorithm will always pick versions that are specified in one module file unless a version that doesn't exist was added by hand. If the algorithm always selects a version specified in modules, then that's a perfectly good place to put hash values.

This should probably be addressed explicitly, but it's only been what, 1 day, since vgo was announced?

Re:Go and Versioning: Minimal Version Selection by bbatha on Wednesday February 21, 2018 @09:15PM (#16434680)
It’s not. But it’s not in the current tool. And as this article devoted a long section to why they’re not required for reproducibility I suspect the go team isn’t planning on added one. It’s especially important to give this feedback early in the process so this critical functionality of the tool is not omitted.
Re:Go and Versioning: Minimal Version Selection by bradfitz on Wednesday February 21, 2018 @10:07PM (#16434870)
Re:Go and Versioning: Minimal Version Selection by bbatha on Wednesday February 21, 2018 @11:15PM (#16435102)
That fixes all of my problems. Great work!