mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
6a3f8ae407
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> |
||
|---|---|---|
| .. | ||
| commands | ||
| rails | ||
| rails_generator | ||
| tasks | ||
| code_statistics.rb | ||
| commands.rb | ||
| console_app.rb | ||
| console_sandbox.rb | ||
| console_with_helpers.rb | ||
| dispatcher.rb | ||
| fcgi_handler.rb | ||
| initializer.rb | ||
| performance_test_help.rb | ||
| rails_generator.rb | ||
| railties_path.rb | ||
| ruby_version_check.rb | ||
| rubyprof_ext.rb | ||
| source_annotation_extractor.rb | ||
| test_help.rb | ||
| webrick_server.rb | ||