Isn't there a method of freezing not just rails, but all gems your project uses?
Seems to me that if you're dealing with an uncooperative host, that's the route you want to go -- those of us with cooperative hosts would probably rather manage things with gems. Often, that's unavoidable -- rmagick, for example. Certainly seems odd to be doing this in a support library. On Tue, Nov 11, 2008 at 5:57 PM, Geoff B <[EMAIL PROTECTED]> wrote: > > On Nov 11, 2:02 pm, "Chad Woolley" <[EMAIL PROTECTED]> wrote: > > Why does it need to be bundled rather than be a normal gem dependency? > > By bundling tzinfo, everything works out of the box -- if you freeze > rails into vendor, you can then deploy anywhere, even on boxes that > don't have rails or tzinfo installed. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
