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
I am working on setting up NTPsec's build system to properly handle Go
code, and can only find limited information of the preferred way of
structuring the directory tree.
Forcing the entire project into GOPATH would be sloppy and a giant kluge
all around.
Placing the go code in a folder with