> So do *not* use go get when manually cloning the project then I take it?
That is correct. For most developers it would be one or more
repositories that contain many modules, not all of which would be
go-gettable anyway.
Also note that "go get" in module mode (outside of GOPATH) will
unpackage w
On 4/17/19 2:50 PM, andrey mirtchovski wrote:
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 (
> 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
