mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
parent
cf88271331
commit
39f2b4f1a4
1 changed files with 14 additions and 0 deletions
|
@ -38,6 +38,20 @@ module Bundler
|
||||||
identifier.hash
|
identifier.hash
|
||||||
end
|
end
|
||||||
|
|
||||||
|
##
|
||||||
|
# Does this locked specification satisfy +dependency+?
|
||||||
|
#
|
||||||
|
# NOTE: Rubygems default requirement is ">= 0", which doesn't match
|
||||||
|
# prereleases of 0 versions, like "0.0.0.dev" or "0.0.0.SNAPSHOT". However,
|
||||||
|
# bundler users expect those to work. We need to make sure that Gemfile
|
||||||
|
# dependencies without explicit requirements (which use ">= 0" under the
|
||||||
|
# hood by default) are still valid for locked specs using this kind of
|
||||||
|
# versions. The method implements an ad-hoc fix for that. A better solution
|
||||||
|
# might be to change default rubygems requirement of dependencies to be ">=
|
||||||
|
# 0.A" but that's a major refactoring likely to break things. Hopefully we
|
||||||
|
# can attempt it in the future.
|
||||||
|
#
|
||||||
|
|
||||||
def satisfies?(dependency)
|
def satisfies?(dependency)
|
||||||
effective_requirement = dependency.requirement == Gem::Requirement.default ? Gem::Requirement.new(">= 0.A") : dependency.requirement
|
effective_requirement = dependency.requirement == Gem::Requirement.default ? Gem::Requirement.new(">= 0.A") : dependency.requirement
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue