The modules Wiki https://github.com/golang/go/wiki/Modules <https://github.com/golang/go/wiki/Modules> is 68 pages long… not sure how such a simple need, solved many times before, ends up needing 68 pages to describe its usage. (I realize that a lot of the text is the FAQ, but still, if you need that long a FAQ, there are probably too many questions…)
> On Dec 12, 2018, at 4:31 PM, Ian Lance Taylor <i...@golang.org> wrote: > > On Wed, Dec 12, 2018 at 8:08 AM Robert Engels <reng...@ix.netcom.com> 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. -- 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.
