If i understand it correctly the proposed solutions does not solve the problem of forking repos. The ideal solution would be to have a import path agnostic of the repo location so that a fork could be up and downstream compatible.
On Thursday, December 13, 2018 at 12:32:11 AM UTC+2, Ian Lance Taylor wrote: > > On Wed, Dec 12, 2018 at 8:08 AM Robert Engels <ren...@ix.netcom.com > <javascript:>> wrote: > > > > I am pretty sure that the correct solution is to decouple the package > from its location. And a global Go registry can tell Go get where that > package can currently be found. > > You don't need a global registry. Or, rather, the global registry can > be DNS. You can set up your own trivial redirector, using a meta tag, > as discussed at https://golang.org/cmd/go/#hdr-Remote_import_paths . > Or you can use an existing general purpose redirector such as > gopkg.in. Either way you can enforce this with an import comment as > discussed at https://golang.org/cmd/go/#hdr-Import_path_checking . > > Ian > -- 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.
