aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/lib/active_support/json/variable.rb
diff options
context:
space:
mode:
authorTim Connor <timocratic@gmail.com>2009-05-21 14:51:34 -0700
committerJeremy Kemper <jeremy@bitsweat.net>2009-06-05 21:54:56 -0700
commit6a3f8ae4075042f122d493208f18ecfb797b38ae (patch)
treeef8c16314ac023752e3cbaa9fb4efb3387b3c718 /activesupport/lib/active_support/json/variable.rb
parentccf70b9570a0bc79bac9dc941eb3cea6b5cc39c2 (diff)
downloadrails-6a3f8ae4075042f122d493208f18ecfb797b38ae.tar.gz
rails-6a3f8ae4075042f122d493208f18ecfb797b38ae.tar.bz2
rails-6a3f8ae4075042f122d493208f18ecfb797b38ae.zip
Work around a gem dependency edge case that prevents Rails from booting..
If you have a frozen gem with unfrozen dependencies (for instance if the dependency has native extensions so can't be frozen) you can have a nightmare upgrade problem, where you cannot rake gems:install, because rake is broken by a gem loading problem. If you bump up your frozen gem to a newer version that requires a newer dependency, everybody else on the team will have rake broken by that dependency mismatch, since you will have had to specify the dependency in your config.gems, otherwise nobody will have installed it, since the parent is frozen. And now the config.gems loading code will kill rake. [#2609 state:committed] Signed-off-by: Jeremy Kemper <jeremy@bitsweat.net>
Diffstat (limited to 'activesupport/lib/active_support/json/variable.rb')
0 files changed, 0 insertions, 0 deletions