Hypothetical example: Say I'm writing an application that uses "rsc.io/quote" and I discover a bug in that package that breaks my software. I would of course clone the quote repository, add a test that demonstrates the bug, fix the bug, and submit a patch to the maintainer.
After making the fix but before submitting the patch, I'd like to first import my local copy of the quote package to ensure my change prevents the problem in my application. How could I do that? Back in the GOPATH days, I could presumably have temporarily used a relative import path: https://pkg.go.dev/cmd/go#hdr-Import_path_syntax I'm not sure how that would work in a post-GOPATH environment. (That page also talks about programs in a "work space" and not in a "work space." Apparently "work space" is a technical term in this context, but I don't know what it means. "go help gopath" doesn't help. What is and isn't a "work space"?) Could I clone the quote repository in a vendor/ directory inside my application directory structure? Are vendor/ directories still used in post-GOPATH environments, or are they considered deprecated or obsolete? Thanks. --PSRC -- 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/CAG%3D3cj%3Duj8csjJsY45Uk81RLZpwhr1xmtgCWU9L4HLuFvpxOoQ%40mail.gmail.com.
