-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
it can't work with gvm #49
Comments
@kelvinji2009 any chance you already have |
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 |
@pote Yup. But i have tried to delete them and it still not works. Then i switch back to homebrew, everything works fine now. |
@pote Maybe go needs a tool like |
@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? |
@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. |
@kelvinji2009 Could you post the affected vars before and after activating gvm and gvp? |
@siddharthist I have already uninstall the gvm because of the conflict. |
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.
The text was updated successfully, but these errors were encountered: