On May 21, 10:44 am, Jian Lin <[email protected]> wrote: > On a Mac running Snow Leopard, the Rails version was 2.3.5 (by using > rails -v) > > and then I used gem install to install about 20 things, and maybe there > was a line on the instructions that was there in the past that says > > gem install rails -v=1.3.5 > > and I ran it anyways, thinking that maybe 1.3.5 is a different version > number... > > and it installed 5 gems (as i remember). > > Will that actually affect the current rails? > > Even after the installation, when I use > > rails -v > > it still says 2.3.5 > > and also if it is > > gem list rails > > it would list something like > > rails (2.3.5, 2.3.2, 1.3.5) > > so looks like they exist nicely with each other without affecting one > another? thanks.
Yup, rubygems is designed to handle that sort of thing. Installed executables (eg the rails executable that sets up a new app) will run the latest version), you can run older versions by doing (for example) rails _1.3.5_ anoldapp The fiddly stuff is when the old version of rails doesn't cope with the version of ruby you have, eg rails didn't handle ruby 1.8.7 before 2.1 (I think, could be a different version but you get the idea) or uses functionality that was deprecated and later removed in newer versions of rubygems. Fred > -- > Posted viahttp://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/rubyonrails-talk?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
