Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Bundler does not respect $GEM_HOME #45

Closed
ashmoran opened this issue Feb 7, 2010 · 4 comments
Closed

Bundler does not respect $GEM_HOME #45

ashmoran opened this issue Feb 7, 2010 · 4 comments

Comments

@ashmoran
Copy link

ashmoran commented Feb 7, 2010

Not sure if this is a bug or not.

I'm using rvm which manages its own gemsets. So if you do 'bundle install', Bundler's default location (in head, as of today) of ~/.bundle means the gems can't be found. Currently I'm having to do:

% bundle install $GEM_HOME

To get the rvm Ruby to see them.

Wayne Seguin seems to think 0.9.3 behaviour was supposed to be to use $GEM_HOME. What's the correct behaviour here?

Cheers - Ashley

@gavinhughes
Copy link

Voted up. "bundle install" installs gems to ~/.gems, creating the directory if none exists. The install should instead default to $GEM_HOME.

@jamiecobbett
Copy link

+1

@carllerche
Copy link
Contributor

bundle install actually installs to ~/.bundle by default. bundle install $GEM_HOME should work as expected on master.

@ashmoran
Copy link
Author

What I found surprising - and I believe gavinhughes and jamiecobbett are thinking the same - is that bundle install $GEM_HOME is not the default. It's really strange doing a bundle install and then not being able to run the software you thought you just installed the gems for.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants