Having an interface between go get and the location of the repositories should really allow people to move packages around at will provided the registration of a package provides a canonical import path. (and a facility for the declaration of mirrors)
Now, to accomodate with vcs and demands for reproducible builds (which require segregation of the dependencies per project), perhaps the go tool could allow switching between multiple $GOPATH. (just to avoid different project builds conflicting at the vcs level). Also binaries may benefit from these changes if they record the source release point they were compiled from. Go gets it mostly right because the canonical package path expect backward compatibility. We shouldn't need SAT solvers to resolve dependencies normally. :) -- 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.
