There's also this: https://github.com/golang/go/issues/37755 -- just retain GOPATH mode
Although, now that I've been using modules more, and my various interdependent packages are more stable, I am more sympathetic to something like #26640 instead of retaining GOPATH. Anyway, having SOME kind of good solution to this distributed workflow scenario would be great! - Randy > On Jan 13, 2021, at 5:53 AM, Wojciech S. Czarnecki <o...@fairbe.org> wrote: > > Dnia 2021-01-13, o godz. 07:22:52 > Rob Pike <r...@golang.org> napisał(a): > >> Also, one must be sure to remove the replace directive before >> releasing the code, which is an easy detail to forget. > > I'd humbly summon https://github.com/golang/go/issues/26640 here. > Opened at the modules advent, still it sees no love from the Team. > > -- > Wojciech S. Czarnecki > << ^oo^ >> OHIR-RIPE > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/20210113145309.61f42301%40xmint. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/E8444AA8-9139-4E57-BC78-44D9A56A0840%40gmail.com.
