Right now we have multiple gem commands in /usr/bin… I guess we really should just drop them, and have a single gem command that uses the selected Ruby by default, just like we have a single rake and so on.
This is now fixed since we always use the unbundled rubygems, right?
No... flame@yamato mytmpfs % qlist rubygems | grep /usr/bin /usr/bin/gem19 /usr/bin/jgem /usr/bin/gemee18 /usr/bin/gem18
How would I install a gem for $not_default then?
(In reply to comment #3) > How would I install a gem for $not_default then? > doing the -v version, I'd hate having to do ruby18 /usr/bin/gem install.. What's the problem with the current setup?
Out of line with the other binaries we install... ruby19 -S gem install Or we'll have to make /usr/bin/ruby a binary respecting RUBY variable.
