On Nov 13, 1:25 pm, Adam Greene <[EMAIL PROTECTED]> wrote: > Geoff, it sounds like there is not an easy solution except perhaps if > you bundle a version like 0.3.11 but rails *requires* 0.3.9, use > ~>0.3.9 for the config.gem version rather than always incrementing it > to 0.3.11.
If ActiveSupport required an older version than what was bundled, you'd run the risk of requiring an older version of the gem that happened to be installed on your system, even if you didn't explicitly declare it via config.gem. I do think we should respect a version explicitly specified via config.gem, even if it's an older version than the bundled one (which we're not doing right now.) Or at least give feedback that we're not respecting the user's declared wishes. I don't know if this would even be possible -- we'd have to somehow introspect the gem requirements, I guess. Fyi, Rails should be compatible with any tzinfo version in the 0.3.x series (and possibly the 0.2.x series, though I haven't tested this recently.) For the most part, the version upgrades are just changes to tzdata; there haven't been any changes to the api in 0.3.x that would affect compatibility. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
