From: Cheri Anaclerio Date: 2008-06-29T22:37:23+09:00 Subject: Re: Ruby 1.9.0/1.8.7/1.8.6/1.8.5 new releases (Security Fix) Thanks, Igal! So when I want to go back to using /usr/bin/ruby and it's associated gems, would I just delete the stow directory $ sudo stow -d /usr/local/stow ruby-1.8.6p230smartleaf I am contemplating the solution of just upgrading to Ruby 1.8.7 and Rails 2.1 since my project is still in development. However, from reading the forums it looks like there are many plugins that won't work with Rails 2.1 and other issues that still need to be resolved. Any thoughts on the upgrade route? - Cheri Igal Koshevoy wrote: > Cheri Anaclerio wrote: >> > The problem is that the copy of RubyGems installed via Yum > (/usr/bin/gem) is using your old interpreter (/usr/bin/ruby) and knows > nothing about your new manually-compiled interpreter > (/usr/local/bin/ruby). > > The solution is to install RubyGems for the new interpreter, e.g.: > > wget http://rubyforge.org/frs/download.php/38646/rubygems-1.2.0.tgz > tar xvfz rubygems-1.2.0.tgz > cd rubygems-1.2.0 > sudo /usr/local/bin/ruby setup.rb --no-ri --no-rdoc > sudo /usr/local/bin/gem install rake --no-ri --no-rdoc > > Because the above changes the stowed directory structure, you'll want to > restow it so that the new files are linked into /usr/local, e.g.: > > pushd /usr/local/stow; sudo stow --restow ruby-1.8.6p230smartleaf; > popd > > There's a way to make multiple Ruby interpreters share a copy of the > installed gems by setting the GEM_HOME environmental variable. However, > this seems like a bad idea and you're best off just installing new > copies of the gems you need. > > -igal -- Posted via http://www.ruby-forum.com/.