Oh I see now. I guess we need something inbetween go get and the different vcs to register and timestamp a package each time it is declared as having been updated. (would still be vcs agnostic though, it's just to timestamp the package files)
Would make releasing a package a bit more of a manual process but it could be a good thing. The tooling should be able then to decide up on the latest vendored package to use. That would also decouple the import paths from "github" as is currently often the case. On Friday, July 29, 2016 at 2:47:20 AM UTC+2, Dave Cheney wrote: > > Yes, to use the vendor/ feature project authors need to flatten all their > dependencies into a single, top level, vendor/ folder. This is currently > difficult as there is no common way to look at two copies of the same > source code and decode if there are the same, and if not, which should take > priority. -- 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.
