hey geoff, > 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.
that actually isn't true. I had tzinfo 0.3.10 installed using rails 2.1.1. that rails version shipped with tzinfo-0.3.9, but it correctly used my config.gem specification and used the 0.3.10 version. The issue arose because I migrated to rails 2.1.2, which came with a partially bundled tzinfo-0.3.11, used that version and ended up breaking my application (thankfully not in production; love those tests!). Chad, I agree with your point about bundling, but at the risk of beating a dead horse, my vote would be to either bundle the full gem (instead of a partial one with broken dependencies) OR do not bundle and just have dependencies (like active-record does on a db-specific gem). Adam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
