> This is all fine and good until the project is fetched with a go get command, > which dumps everything directly into GOPATH, thereby preventing it from > fetching dependencies.
If you are fetching it with "go get" then that's presumably because it's a dependency required by another package or module, in which case the go command will use the correct place for it based on whether "go get" was run inside a module directory (then it goes in the module cache) or anywhere else (then it goes into GOPATH). If you are not fetching the project as part of a dependency, because you want to work on it, modify it, etc, then you can clone it anywhere outside GOPATH on your system and don't need to use "go get". One of the use cases for go modules was to allow projects to reside everywhere on the filesystem to allow legacy directory layouts to be used when developing. -- 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.
