gem install can be passed a version argument, so just install the version your application.rb has listed. Trying to bring up a Rails 2.3.x app under 3.1.3 is way too many moving parts for anyone. Yes, you should update, but just get it running and passing its tests under the original version before you try that.
Walter On Dec 26, 2011, at 7:36 PM, ari g. wrote: > Thanks for the help, Walter. > > The more I work on this, the more I see that my problem is one of trying > to get old code up and running. I'm going to try that Bundler trick, > just to see what it does but that page describes how to get it running > in Rails 2.3 and a 'sudo gen install rails' brought in Rails 3.1.3. > Hopefully it'll still work but I think I'm going to pause a bit in my > efforts with that gem_original_require error and look at what the web > has to say about legacy (i.e. old) rails apps. > > Thanks again! > > ~ari > > -- > Posted via http://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 at > http://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.
