On Tue, Feb 20, 2018 at 2:35 PM, Devon H. O'Dell <devon.od...@gmail.com> wrote:
> With regards to minimum version selection, if I depend on some feature > present, this comes with two implicit dependencies: correctness and > safety. My knee-jerk reaction here is that the time folks spend > "telling the package manager, 'no, use at least Y,'" will largely be > in response to these sorts of issues. Maybe this is seen as "working > as intended;" my feeling is that this will become tiresome for > projects with large dependency chains. Might it be worthwhile (and > automatically possible) to pick the "maximally correct" minimum > version? > I am not sure what you mean by "maximally correct". I think that's approximately what all the other package managers try to do. It makes things very complex (literally: research.swtch.com/version-sat). Note that it's still super easy to say "update this package to latest" or "update everything to latest". It just only happens when you ask, not when the tool feels like it. Russ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
