cleaning up older rails installs on Mac OS X Snow Leapord

rubyonrails-talk
1

I am currently wanting to cleanup my gems so that i end up with Rails 2.3.11 and Rails 3.0.x. While working on this I notice I cannot uninstall some Rails versions from command line. I ran the following and wonder if it is safe for me to remove Rails 1.2.6, 2.2.2 and 2.3.5 versions from these folders on my Mac.

rails (3.0.7, 3.0.6, 3.0.5, 3.0.3, 3.0.0, 2.3.11, 2.3.8, 2.3.5, 2.2.2, 1.2.6)     Author: David Heinemeier Hansson     Rubyforge: http://rubyforge.org/projects/rails     Homepage: http://www.rubyonrails.org     Installed at (3.0.7): /Library/Ruby/Gems/1.8                  (3.0.6): /Library/Ruby/Gems/1.8                  (3.0.0): /Library/Ruby/Gems/1.8                  (2.3.11): /Library/Ruby/Gems/1.8                  (2.3.5): /System/Library/Frameworks/Ruby.framework/ Versions/1.8/usr/lib/ruby/gems/1.8                  (2.2.2): /System/Library/Frameworks/Ruby.framework/ Versions/1.8/usr/lib/ruby/gems/1.8                  (1.2.6): /System/Library/Frameworks/Ruby.framework/ Versions/1.8/usr/lib/ruby/gems/1.8

2

I just ran into this last night. Since I use rvm for my gems now, I ended up using 'gem uninstall rails' (outside of rvm) and choosing to uninstall all of the available versions. I manually nuked the gem repos under /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ lib/ruby/gems/1.8. HOWEVER, I am unsure what ramifications this will have outside of my rvm world. I'm thinking specifically of MacRuby.

YMMV, I'm not responsible for you breaking your machine. :wink:

Beren

3

I am currently wanting to cleanup my gems so that i end up with Rails

2.3.11 and Rails 3.0.x. While working on this I notice I cannot

uninstall some Rails versions from command line. I ran the following

and wonder if it is safe for me to remove Rails 1.2.6, 2.2.2 and 2.3.5

versions from these folders on my Mac.

Sounds like no fun. I would recommend just starting to use rvm, and forget about the mess. Rvm isolates your rubies, and gems so you wont have interference from the system installs.

4

I am currently wanting to cleanup my gems so that i end up with Rails

2.3.11 and Rails 3.0.x. While working on this I notice I cannot

uninstall some Rails versions from command line. I ran the following

and wonder if it is safe for me to remove Rails 1.2.6, 2.2.2 and 2.3.5

versions from these folders on my Mac.

Sounds like no fun. I would recommend just starting to use rvm, and forget about the mess. Rvm isolates your rubies, and gems so you wont have interference from the system installs.

Ps, when I say rvm, also mean that in rvm you can create gemsets. Many create a gemset for each project, so the dependencies of each project are seperate. Rvm also lets you insall as many versions of ruby that exist. As far as what you leave on your mac, the only thing you need to install rvm is one ruby, does not matter the version. As for all the other versions of rails you should be able to delete them or leave the as you like.

5

I have been using RVM, Homebrew and POW in combination with projects using Rails 2.3.11 retrofitted with Bundler and then separate projects using Rails 3.0.x. Between my homebrew installs of MySQL, POW and passenger issues depending on whether you use RVM and/or try to use Rails 2.3.11.... It has been fun to say the least. I have some issues with the Mysql gem with one of my gemsets and have been trying to see why one of my sites will run under RVM system, but not correctly under the RVM gemset I created for the app. I was hoping to clean up my system gems and move towards using more RVM sets but sometimes you break more than you cleanup. In the end, I will probably leave my system intact and use RVM for new projects going forward. Still, there is the part of my brain that wonders why Rails 1.2.6 and 2.2.2 are installed in their current locations. I have a tendency to poke around places that were not meant to be poked in it seems.