Hi Maurizio,
I tend to use go vendoring for this purpose.
I set GOPATH to $HOME, and this is my "global" environment. Each
project is checked out to its module path.
Instead of using 'go get' to get dependencies, I use git submodules via
vendetta. This checks out all of the dependencies for ea
For projects that are mostly not go (or go is a component anyway) you could
do $HOME/project/src/ and then point $GOPATH=$HOME/project.
You can use 2 different segments in $GOPATH (GOPATH=/foo/bar:/bar/foo) and
go get will place go gettable packages in the first segment of $GOPATH.
On Thu, Sep 1,
hello gophers,
How people do use GOPATH?
having a single workspace for all my projects doesn't really work for me.
Some project might involve more than a go portion and really shoehorning
them into a go tree doesn't sound right.
I'm completely fine with switching GOPATH every time I switch proje
