> Anyway, as I have mentioned before, this solves nothing when multiple
> versions of a nested dependency is needed by project dependencies.
This is a problem that's solved by vgo. Have a look into that.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
Indeed it is possible to set the $GOPATH in a shell. And if I use other
tools with a specific project, for example VSCode, then I have to start all
of them from the same terminal. Which is not the most desirable outcome.
Anyway, as I have mentioned before, this solves nothing when multiple
ver
Il giorno giovedì 19 aprile 2018 14:48:09 UTC+2, Kaveh Shahbazian ha
scritto:
>
> Is it possible to tell go tools to get the go-path from a source other
> than $GOPATH?
>
>
No, but you can of course set the GOPATH environment variable for the go
tool.
As an example, on an UNIX shell:
$ GOPATH=$
