On 10/31/07, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > > I'm flexible, if you want me to rewrite it to not have the > > 'preinitializers' directory and instead just have a magic hook > > filename, I'm glad to rewrite the patch. Just let me know. > > My problem is that to add an entire pre-initializer feature when the > sole use case is version twiddling seems hugely overkill. No one's > come up with a case that can't be solved by moving things into and out > of vendor/rails...
The use case is selecting the version _without_ modifying the app. I want _easily_ test my app against multiple rails versions under Continuous Integration. Having my CI tool simply set an environment var is easy. Having it install plugins or hack externals is much harder, relatively. > > If all you want to do is have more control over the version of rails > that gets required, let's do that Sure, we could have the RAILS_GEM_VERSION allow a version spec (>) instead of just a numeric version. However, this still wouldn't support even cooler preinit hooks that I haven't even mentioned to avoid confusion (like automatically installing the required gem if it's missing) >... instead of some generic thing that > we'll have to support for an entire release cycle. What's to support? It will be completely transparent to people who don't use it. If it's the existence of the directory that's a problem, I'm fine to go with the single magic hook file (e.g., config/preinitialize.rb) > > -- > Cheers > > Koz Thanks for the feedback, -- Chad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
