Skip to content
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

location of .godeps folder #27

Closed
tcurdt opened this issue Apr 27, 2015 · 7 comments
Closed

location of .godeps folder #27

tcurdt opened this issue Apr 27, 2015 · 7 comments
Milestone

Comments

@tcurdt
Copy link

tcurdt commented Apr 27, 2015

Maybe a little esoteric for most people - but I am trying to build a go project on a read-only filesystem.
Would be great to have command line option to change the location of the .godeps folder.

@tcurdt
Copy link
Author

tcurdt commented Apr 30, 2015

Would you accept a pull request for this?

@pote
Copy link
Owner

pote commented Apr 30, 2015

Good question, I think I would since the implementation would be simple: I can imagine a use case like source gvp in .other_directory, if you feel like implementing it I think I'll merge it right away.

The thing is: my use case for gvp is now usually solved by simply using export and source

$ export GOPATH="$PWD"/.godeps:"$PWD"

In most cases I don't even do that much and instead just put that same line in the .env file for my projects, and then run source .env to load the GOPATH and any other env variables my app uses.

Maybe this means I'm not the best person to maintain gvp anymore, since I really barely use it, I'll have to think about that.

@tcurdt
Copy link
Author

tcurdt commented Apr 30, 2015

Actually I didn't realize it's that simple. Seems like I can just do

$ export GOPATH="/tmp/godeps:$PWD"

and be done with it. That indeed questions the need of gvp.
And I am not a big fan sourcein anyway.
I think I prefer the explicit export as well.

@pote
Copy link
Owner

pote commented Apr 30, 2015

Exactly, gvp was written before I started working in that way, but these days I use it only very ocasionally, hence the little effort in improving the tool. :)

@langston-barrett
Copy link
Collaborator

@tcurdt Are you still interested in this feature? Should this issue be closed?

@tcurdt
Copy link
Author

tcurdt commented Jul 22, 2015

I think this should just be properly documented - but for me I am happy to close this issue.

@tcurdt tcurdt closed this as completed Jul 22, 2015
@langston-barrett
Copy link
Collaborator

@tcurdt It would be awesome if you'd like to submit a PR for documentation.

@langston-barrett langston-barrett modified the milestone: v0.3.0 Jul 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants