So the decision is hardwired in the go tooling binaries.
In any case, this bug report is about giving a more low level or granular way to compile go stuff so that you can decide to build diferently in case the go tooling does not do what you want.
Alternatively, the snapcraft go plgin should maybe clone the go build environment in a isolated build path so that changes are possible to it when needed.
I tested go 1.7 (by installing binaries, as we don't have it in xenial yet) and now you can snap godoc as it installs to $GOPATH.
If you visit /github. com/golang/ go/issues/ 15106
https:/
You can see the fix for go 1.7 here: /go-review. googlesource. com/#/c/ 21701/3/ src/cmd/ go/pkg. go
https:/
So the decision is hardwired in the go tooling binaries.
In any case, this bug report is about giving a more low level or granular way to compile go stuff so that you can decide to build diferently in case the go tooling does not do what you want.
Alternatively, the snapcraft go plgin should maybe clone the go build environment in a isolated build path so that changes are possible to it when needed.
I tested go 1.7 (by installing binaries, as we don't have it in xenial yet) and now you can snap godoc as it installs to $GOPATH.