diff options
| author | Homu <homu@barosl.com> | 2016-08-25 23:12:53 +0900 |
|---|---|---|
| committer | Homu <homu@barosl.com> | 2016-08-25 23:12:53 +0900 |
| commit | 8513ed1481dde5b47eead96dd0a1cfe3d77c4c84 (patch) | |
| tree | d4e961360ad9e4986cdcb6332b69581299ca9dbe /lib/bundler/source.rb | |
| parent | 92aa19d8c979db9ccf54edfa172c4a9f7a6382de (diff) | |
| parent | 2b3e175c13ddae4e95764b745e1589fbc1131dd1 (diff) | |
| download | bundler-8513ed1481dde5b47eead96dd0a1cfe3d77c4c84.tar.gz | |
Auto merge of #4654 - bundler:aa-ruby-version-conflict-message, r=indirect
Add resolver-style error messages for required Ruby conflicts
*Proposal:* When a gem in the Gemfile requires a Ruby version different than the Gemfile's `ruby`, print a conflict error message that looks more or less exactly like any other resolution conflict error.
*Current behavior:* On `master` today, Bundler will ignore the gem's required_ruby_version until install-time, and raise an exception like "require_ruby-1.0 requires ruby version > 9000, which is incompatible with the current version`.
After #4650 has been merged, Bundler will correctly reject gems that require a different version of Ruby, and instead print the error "Could not find `required_ruby` in any of the sources in your Gemfile".
*Rationale for change:* I believe that error message is surprising and misleading. The source _does_ contain `required ruby`, and I think we'll get bug reports about how our error message is wrong.
Diffstat (limited to 'lib/bundler/source.rb')
0 files changed, 0 insertions, 0 deletions