I read through quite a bit of those docs, but somehow missed that - thanks Daniel.
On Tuesday, February 27, 2018 at 4:35:32 PM UTC-7, Daniel Theophanes wrote: > > Hi Robert, you still can do that. Just add a "replace" directive in the > local go.mod. > > Please see https://research.swtch.com/vgo-tour for more details. > > On Tuesday, February 27, 2018 at 1:47:40 PM UTC-8, Robert Carlsen wrote: >> >> Before with the naive GOPATH workflow and also with vendoring, it was >> super easy for me to debug problems with and contribute to upstream >> packages. With vgo, I can't just cd into vendor/github.com/foo/bar to >> test out fixes for bugs, etc. Without vendoring I could just cd into >> $GOPATH/src/github.com/foo/bar, test a patch - commit, push - and submit >> a PR to the 3rd party project. With vgo, I now have to fork+clone that >> repository, modify my go.mod file to point to my fork, patch my clone, >> commit and push to my fork before I can rebuild and test the patch. Yuck. >> > -- 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.
