If someone looks for an alternative, consider this kit:<p><a href="https://github.com/pote/gvp" rel="nofollow">https://github.com/pote/gvp</a> - virtualenv in go's world<p><a href="https://github.com/pote/gpm" rel="nofollow">https://github.com/pote/gpm</a> - pip in go's world
I'm curious why so many of these Go dependency managers are popping up. Doesn't go get download all dependencies automatically? Why are these third-party dependency managers necessary?
In case anyone is interested, we open sourced this one about a year ago: <a href="https://github.com/VividCortex/johnny-deps" rel="nofollow">https://github.com/VividCortex/johnny-deps</a>
It says it is inspired by Bundler but in what ways? I am curious as I didn't use much of neither bundler nor goop but I have heard the constraints resolution lays in the heart of bundler.
set -x GOPATH (PWD)/.vendor
set -x GOBIN (PWD)/.vendor/bin<p>And committing stuff in git when it matters.<p>gvm is also nice for testing stuff with different versions of go.
I've been doing basically the same thing by creating src/ and pkg/ directories and using this alias:<p>go='GOPATH=`pwd`:$GOPATH go'
Goop for teh rescue! The only trouble I had with go is the dependency handling. I wish people realize how Erlang's way of dealing with this is superior.