First let’s list 2 truths here:
- Rails 2.3.5 will fail with RubyGems 1.5.0 +
- Rails 2.3.11 will fail with RubyGems 1.7.0 +
So what if you want to deploy or run an application which unfortunately still or initially written in rails 2, given the situation that latest RVM default install rubygems version 1.8.11? It turns out to be not so painful, cause it’s as simple as just issue one command (take 1.4.2 for example): [cc lang=”ruby”] gem update –system 1.4.2 [/cc] Just like the China highway train, sometimes what you need to do is just to stop moving so fast.
