From: Jonathan Nielsen Date: 2010-05-01T06:42:44+09:00 Subject: Re: Setting to Ruby 1.9 in Ubuntu... Try 'sudo gem install rvm' This will put the rvm-install in your path. -Jonathan Nielsen On Fri, Apr 30, 2010 at 3:40 PM, Walton Hoops wrote: > On 4/30/2010 2:22 PM, Xeno Campanoli / Eskimo North and Gmail wrote: >> Walton Hoops wrote: >>> On 4/30/2010 1:36 PM, Xeno Campanoli / Eskimo North and Gmail wrote: >>>> I tried installing a bunch of ruby 1.9 stuff on my Ubuntu laptop last >>>> night, but my default ruby is still 1.8.7.  Anybody know a regular >>>> method for setting to 1.9 on Ubuntu?  Perhaps this is an Ubuntu >>>> question, but presumably the best way is not always the Ubuntu >>>> way...??? >>> The Ubuntu way is to run 'sudo update-alternatives --config ruby' and >>> 'sudo update-alternatives --config rubygems', or instead of calling Ruby >>> scripts with 'ruby', call them with 'ruby1.9' when you want them run >>> in 1.9. >>> >>> Another solution that is available is Ruby Version Manager (RVM).  I've >>> never used RVM, so I can't say anything for or against it. >>> http://rvm.beginrescueend.com/ >>> >>> >> >> Thank you.  That didn't get me there, but I really appreciate the >> quick response, and that actually helps me in some other areas. >> >> I got this: >> >> root@rockhopper:~# update-alternatives --config ruby >> update-alternatives: error: no alternatives for ruby. >> root@rockhopper:~# update-alternatives --config rubygems >> update-alternatives: error: no alternatives for rubygems. >> root@rockhopper:~# >> >> rvm in that guise is not on my apt purvey.  I appreciate the >> suggestions. Perhaps if it's this hard it's better to wait for the OSs >> to upgrade themselves anyway.  I just noticed the CentOS we use is way >> back to ruby 1.8.5.  I sure hope we stop using CentOS soon.  It is a >> dog, and wastes a lot of our time. Debian family stuff has it's >> problems, but for my work it seems to always come out as superior. >> > Ugh.  I just assumed that Ruby would be managed through the > alternatives.  This is why I run from source. > > The lazy man's solution to your problem is to simply change the symbolic > link 'ruby' in /usr/bin to point to 'ruby1.9' instead of 'ruby1.8' (the > same would need to be done for rubygems.  Make sense? > >