On Wed, Nov 12, 2008 at 3:42 AM, David Masover <[EMAIL PROTECTED]> wrote: > On Tue, Nov 11, 2008 at 7:11 PM, Geoff B <[EMAIL PROTECTED]> wrote: >> >> Also, Tzinfo is not the only non-Rails dependency: see the vendor >> directories in ActionMailer, ActionController and ActiveSupport. Do >> you suggest that Rails unbundle TMail, Builder, XmlSimple, etc., and >> add them as dependencies to the rails gem? > > I would, unless they have patches which haven't made it upstream. And in > that case, I'd break them out into rails-tmail, rails-builder, etc. > > Assuming gem freezing works, what is the reason not to do that? > If gem freezing is broken, why not fix it? > > That's a real question -- there may be a good reason. I'm new here.
The bundled gems already favour installed gems if user's have them. The rationale for bundling them is that they're not a dependency to use *all* of rails, just a small piece of functionality (e.g. the memcache cache store). There's no practical benefit to be gained by changing this policy, the new config.gems code will already provide information to people who make this same 'mistake' again. > > > -- 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 -~----------~----~----~----~------~----~------~--~---
