On Tue, Nov 11, 2008 at 4: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. >
Right, but why is tzinfo special? Because it is the only "non-rails" dependency for rails itself. Seems like the root cause of the problem is that rails freeze command is broken, because it does not freeze the entire dependency graph of rails, which includes tzinfo. Instead, the rails freeze command should freeze whatever version of the tzinfo gem is specified by the current version of activesupport. Then, you get all the benefits and no problems: 1. Rails is not packaging a hacked version of tzinfo 2. Since tzinfo is not bundled, you don't need to use a hacked smaller version, you can just depend on the real gem 3. People who want to manage tzinfo via gems using whatever version they want can do so (which is the original bug report here) 4. People who want to freeze rails will automatically get the real, correct version of tzinfo frozen as well - and shouldn't care if this is big, because people who freeze gems will have ginormous apps regardless... -- 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
