This is a general question about package-user expectations, just wondering if I can confirm an idea.
Suppose this scenario: 1. A user "foo-user" pins a go package "foo-package" to some old point "version-D" (maybe by checking out an old commit). 2. "foo-user" also has a dependency on "bar-package", but didn't pin it down - "bar-package" builds/runs fine with "foo-package" at "version-D" 3. "bar-package" uses new APIs in "foo-package" that are not available in "version-D", and merges into HEAD I would expect that the standard option "foo-user" now has is to also pin "foo-package" to a previous point. Is this the standard option "bar-package" creators can give? thanks -- 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.
