I'm careful to create separate gemsets for each project, so when I run
bundle install, it only installs gems for that gemset. This way gems
dont creep into the wrong projects. Now I just pulled a project from
github. I made sure I was in the correct gemset, and then I run bundle
install and it
On May 18, 2013, at 1:19 PM, John Merlino wrote:
I'm careful to create separate gemsets for each project, so when I run
bundle install, it only installs gems for that gemset. This way gems
dont creep into the wrong projects. Now I just pulled a project from
github. I made sure I was in the
I guess you have installed rake in your `global` gemset for the ruby
version you are using.
Go outside the project and run `rvm use ruby version@global` and then
`gem list`. If you see rake in the list, that means you have it in the
global gemset. No matter which gemset you use with the ruby
Bundler is present in the global gemset. What I usually do is rvm gemset
use @global and then do a gem uninstall bundler
On May 18, 2013 10:51 PM, John Merlino stoici...@aol.com wrote:
I'm careful to create separate gemsets for each project, so when I run
bundle install, it only installs gems
4 matches
Mail list logo