it can't work with gvm

[kelvinji2009]

I install go 1.5.3 by gvm recently. Before this i used homebrew to install go.
After switch to gvm, gvp can't work correctly. go get did not download the package in first directory listed from GOPATH.
Please see the log from terminal.

---

★  server git:(kdev) ⚡️  »echo $GOPATH
/Users/kelvinji/.gvm/pkgsets/go1.5.3/global
★  server git:(kdev) ⚡️  »source gvp in
>> Local GOPATH set.
(gvp)★  server git:(kdev) ⚡️  »echo $GOPATH
/Users/kelvinji/mitnick/dev/github/go-starter-kit/server/.godeps:/Users/kelvinji/mitnick/dev/github/go-starter-kit/server:/Users/kelvinji/.gvm/pkgsets/go1.5.3/global
(gvp)★  server git:(kdev) ⚡️  »cat Godeps
github.com/itsjamie/go-bindata-templates 65d795d0c74021e19b2ebadf3c83c01a8290a405
github.com/elazarl/go-bindata-assetfs 57eb5e1fc594ad4b0b1dbea7b286d299e0cb43c2
github.com/mattn/go-colorable 9cbef7c35391cca05f15f8181dc0b18bc9736dbb
github.com/mattn/go-isatty 56b76bdf51f7708750eac80fa38b952bb9f32639
github.com/moul/http2curl 1812aee76a1ce98d604a44200c6a23c689b17a89
github.com/nu7hatch/gouuid 179d4d0c4d8d407a32af483c2354df1d2c91e6c3
github.com/olebedev/config e3edea7d68b76222b5118cc2e1cf3825e30abb80
gopkg.in/olebedev/go-duktape-fetch.v2 2cb38c455cc667cf4db0e0547336b5df82913971
gopkg.in/olebedev/go-duktape.v2 1c5e9d0fb82296a24a63ab68b682c5b4d7a45cca
gopkg.in/yaml.v2 f7716cbe52baa25d2e9b0d0da546fcf909fc16b4
github.com/codegangsta/cli v1.2.0
github.com/parnurzeal/gorequest v0.2.13
github.com/labstack/echo v2.0.0-apha1
(gvp)★  server git:(kdev) ⚡️  »tree .godeps
.godeps
├── bin
├── pkg
└── src

3 directories, 0 files
(gvp)★  server git:(kdev) ⚡️  »go get -u -d github.com/codegangsta/cli
(gvp)★  server git:(kdev) ⚡️  »tree .godeps
.godeps
├── bin
├── pkg
└── src

3 directories, 0 files
(gvp)★  server git:(kdev) ⚡️  »

[pote]

@kelvinji2009 any chance you already have github.com/codegangsta/cli in your global GOPATH?

[pote]

Still, a nice use case to reflect on why a per-project GOPATH should not include the global GOPATH IMO, which is gvp's current default behaviour.

Maybe this is a good opportunity to consider a flag or some other mechanism to allow both approaches? I'll defer such decisions to @siddharthist though.

Nowadays I solve this by keeping

export GOPATH=$(PWD)/.dependencies:$(PWD)

(among other configuration values) in a per-project file, and running source <file> whenever I open a terminal to work on a given project.

[kelvinji2009]

@pote Yup. But i have tried to delete them and it still not works. Then i switch back to homebrew, everything works fine now.

[kelvinji2009]

@pote Maybe go needs a tool like NPM to manage the dependencies.

[langston-barrett]

@kelvinji2009 Any ideas why gvm might not work well with GVP? I don't know much about it, myself. Do you think it would be worth adding a flag to either keep or overwrite the global GOPATH?

[kelvinji2009]

@siddharthist GVM adds a lot of ENVs and i did not figure out why not work. I think it's worth adding a flag to fix it for the users of GVM. But i more agreed with @pote , just forget the global GOPATH and overwirte the GOPATH with current directory. If you are maintaining many go projects at the same time, global packages may have a conflict too.

[langston-barrett]

@kelvinji2009 Could you post the affected vars before and after activating gvm and gvp?

[kelvinji2009]

@siddharthist I have already uninstall the gvm because of the conflict.