2009/3/17 “Wolas!” [email protected]:
When you followed gregs advice you ended up sort of “fooling” the ruby
command. now you have two of everything (2 rails gems, one under 1.8
and one under 1.9).
There’s no such thing as a “ruby command” (at least not in my shell).
There is a ruby binary, and there’s a path that might find it
depending on where you put it and what directories your path contains.
Being able to change the path so it can find a different ruby binary
other than the one that came with the system is a feature of the
system, seriously… no fooling. You can have your entire ruby
toolchain living out of /some/place/weird while completely ignoring
the ruby that came with the system, you only have to adjust the paths
to include the weird place. That’s how it works, it’s not magic, no
make sure you are calling the correct gem from the correct place. If i
were you, i would uninstall one of your ruby instalations (at this
That’s all together not necessary. I suspect all of my development
systems have two ruby installs. I ignore the one that came with the
system and install my own whereever I want. I update my bashrc so it
knows about my intentions and that’s about it.