I create a gemset with
$ rvm gemset create r3
$ rvm gemset use r3
$ gem install rails -v3.2.13
At this point
$ rails -v
now shows
$ Rails 3.2.13
but every time I do bundle with a project I've forked, I find that
rails -v
shows Rails 4.0.1
- which then gives issue with the project in question when running tests
(4.0.1
conflicts with 3.2.13
).
My question is - if my Gemfile only has:
$ cat Gemfile
source 'https://rubygems.org'
gemspec
how is this happening? How can I make my command line ruby version stay at 3.2.13
and not switch to 4.0.1
Once it switches to 4.0.1
I seem to be stuck with that for that gemset and to create a 3.2.13
gemset I have to start over again.