> This would allow dynamic control over RAILS_GEM_VERSION and the > Version Specification passed to the RubyGems 'gem' method for the > rails gem. For example, users could test an app or plugin in a > Continuous Integration environment which performs automated regression > testing against various old Rails versions.
I'm just not sure that there are a whole lot of use cases that need this kind of flexibility before environment.rb gets hit. When I'm testing my apps against multiple rails releases I just use symlinks in /vendor/rails pointing to various subversion checkouts. Are there any other common cases you have in mind? You could always automate the patching of boot.rb for your gem installer app. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
