Is it possible to tell go tools to get the go-path from a source other than $GOPATH?
Notes: Assuming the answer is no, I wish it was possible. For example when running a go command from the current directory, it go search the current directory, or goes up, until it finds a (for example) *.goenv* file, in which the GOPATH for current directory is specified. And the system-wide $GOPATH would act as a fall-back option, an umbrella root. This way the current project can have all of its stuff under the directory that contains the specified .goenv without interfering with other packages. Now if the current package (A) has two dependencies B and C and B uses a different version of C, then B can simply resides in a parallel directory to the current directory and be found in the system-wide $GOPATH. But go tools would always look for .goenv first. Seems to occupy the same amount of disk space as any other way of managing packages. -- 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.
