You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
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
The text was updated successfully, but these errors were encountered: