2018-11-02 23:07:56 +00:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
|
|
RSpec.describe "bundle install with install-time dependencies" do
|
2020-12-08 16:36:29 +09:00
|
|
|
before do
|
|
|
|
build_repo2 do
|
2021-04-15 12:47:04 +09:00
|
|
|
build_gem "with_implicit_rake_dep" do |s|
|
|
|
|
s.extensions << "Rakefile"
|
|
|
|
s.write "Rakefile", <<-RUBY
|
|
|
|
task :default do
|
|
|
|
path = File.expand_path("../lib", __FILE__)
|
|
|
|
FileUtils.mkdir_p(path)
|
|
|
|
File.open("\#{path}/implicit_rake_dep.rb", "w") do |f|
|
|
|
|
f.puts "IMPLICIT_RAKE_DEP = 'YES'"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
RUBY
|
|
|
|
end
|
|
|
|
|
|
|
|
build_gem "another_implicit_rake_dep" do |s|
|
|
|
|
s.extensions << "Rakefile"
|
|
|
|
s.write "Rakefile", <<-RUBY
|
|
|
|
task :default do
|
|
|
|
path = File.expand_path("../lib", __FILE__)
|
|
|
|
FileUtils.mkdir_p(path)
|
|
|
|
File.open("\#{path}/another_implicit_rake_dep.rb", "w") do |f|
|
|
|
|
f.puts "ANOTHER_IMPLICIT_RAKE_DEP = 'YES'"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
RUBY
|
|
|
|
end
|
|
|
|
|
2020-12-08 16:36:29 +09:00
|
|
|
# Test complicated gem dependencies for install
|
|
|
|
build_gem "net_a" do |s|
|
|
|
|
s.add_dependency "net_b"
|
|
|
|
s.add_dependency "net_build_extensions"
|
|
|
|
end
|
|
|
|
|
|
|
|
build_gem "net_b"
|
|
|
|
|
|
|
|
build_gem "net_build_extensions" do |s|
|
|
|
|
s.add_dependency "rake"
|
|
|
|
s.extensions << "Rakefile"
|
|
|
|
s.write "Rakefile", <<-RUBY
|
|
|
|
task :default do
|
|
|
|
path = File.expand_path("../lib", __FILE__)
|
|
|
|
FileUtils.mkdir_p(path)
|
|
|
|
File.open("\#{path}/net_build_extensions.rb", "w") do |f|
|
|
|
|
f.puts "NET_BUILD_EXTENSIONS = 'YES'"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
RUBY
|
|
|
|
end
|
|
|
|
|
|
|
|
build_gem "net_c" do |s|
|
|
|
|
s.add_dependency "net_a"
|
|
|
|
s.add_dependency "net_d"
|
|
|
|
end
|
|
|
|
|
|
|
|
build_gem "net_d"
|
|
|
|
|
|
|
|
build_gem "net_e" do |s|
|
|
|
|
s.add_dependency "net_d"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
Fix some bundler specs (#2380)
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
2019-08-20 02:46:31 +02:00
|
|
|
it "installs gems with implicit rake dependencies" do
|
2018-11-02 23:07:56 +00:00
|
|
|
install_gemfile <<-G
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "with_implicit_rake_dep"
|
|
|
|
gem "another_implicit_rake_dep"
|
|
|
|
gem "rake"
|
|
|
|
G
|
|
|
|
|
|
|
|
run <<-R
|
|
|
|
require 'implicit_rake_dep'
|
|
|
|
require 'another_implicit_rake_dep'
|
|
|
|
puts IMPLICIT_RAKE_DEP
|
|
|
|
puts ANOTHER_IMPLICIT_RAKE_DEP
|
|
|
|
R
|
|
|
|
expect(out).to eq("YES\nYES")
|
|
|
|
end
|
|
|
|
|
2021-04-15 12:47:04 +09:00
|
|
|
it "installs gems with implicit rake dependencies without rake previously installed" do
|
|
|
|
with_path_as("") do
|
|
|
|
install_gemfile <<-G
|
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
|
|
|
gem "with_implicit_rake_dep"
|
|
|
|
gem "another_implicit_rake_dep"
|
|
|
|
gem "rake"
|
|
|
|
G
|
|
|
|
end
|
|
|
|
|
|
|
|
run <<-R
|
|
|
|
require 'implicit_rake_dep'
|
|
|
|
require 'another_implicit_rake_dep'
|
|
|
|
puts IMPLICIT_RAKE_DEP
|
|
|
|
puts ANOTHER_IMPLICIT_RAKE_DEP
|
|
|
|
R
|
|
|
|
expect(out).to eq("YES\nYES")
|
|
|
|
end
|
|
|
|
|
2018-11-02 23:07:56 +00:00
|
|
|
it "installs gems with a dependency with no type" do
|
2020-05-08 14:19:04 +09:00
|
|
|
skip "incorrect data check error" if Gem.win_platform?
|
|
|
|
|
2018-11-02 23:07:56 +00:00
|
|
|
build_repo2
|
|
|
|
|
|
|
|
path = "#{gem_repo2}/#{Gem::MARSHAL_SPEC_DIR}/actionpack-2.3.2.gemspec.rz"
|
2019-12-14 19:49:16 +09:00
|
|
|
spec = Marshal.load(Bundler.rubygems.inflate(File.binread(path)))
|
2018-11-02 23:07:56 +00:00
|
|
|
spec.dependencies.each do |d|
|
|
|
|
d.instance_variable_set(:@type, :fail)
|
|
|
|
end
|
|
|
|
File.open(path, "w") do |f|
|
|
|
|
f.write Gem.deflate(Marshal.dump(spec))
|
|
|
|
end
|
|
|
|
|
|
|
|
install_gemfile <<-G
|
2019-05-06 18:06:21 +02:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "actionpack", "2.3.2"
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(the_bundle).to include_gems "actionpack 2.3.2", "activesupport 2.3.2"
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "with crazy rubygem plugin stuff" do
|
|
|
|
it "installs plugins" do
|
|
|
|
install_gemfile <<-G
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "net_b"
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(the_bundle).to include_gems "net_b 1.0"
|
|
|
|
end
|
|
|
|
|
Fix some bundler specs (#2380)
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
2019-08-20 02:46:31 +02:00
|
|
|
it "installs plugins depended on by other plugins" do
|
2021-02-01 16:17:16 +01:00
|
|
|
install_gemfile <<-G, :env => { "DEBUG" => "1" }
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "net_a"
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(the_bundle).to include_gems "net_a 1.0", "net_b 1.0"
|
|
|
|
end
|
|
|
|
|
Fix some bundler specs (#2380)
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
2019-08-20 02:46:31 +02:00
|
|
|
it "installs multiple levels of dependencies" do
|
2021-02-01 16:17:16 +01:00
|
|
|
install_gemfile <<-G, :env => { "DEBUG" => "1" }
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "net_c"
|
|
|
|
gem "net_e"
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(the_bundle).to include_gems "net_a 1.0", "net_b 1.0", "net_c 1.0", "net_d 1.0", "net_e 1.0"
|
|
|
|
end
|
|
|
|
|
2020-05-08 14:19:04 +09:00
|
|
|
context "with ENV['BUNDLER_DEBUG_RESOLVER'] set" do
|
|
|
|
it "produces debug output" do
|
|
|
|
gemfile <<-G
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2020-05-08 14:19:04 +09:00
|
|
|
gem "net_c"
|
|
|
|
gem "net_e"
|
|
|
|
G
|
|
|
|
|
2021-02-01 16:17:16 +01:00
|
|
|
bundle :install, :env => { "BUNDLER_DEBUG_RESOLVER" => "1", "DEBUG" => "1" }
|
2020-05-08 14:19:04 +09:00
|
|
|
|
2020-12-15 08:32:54 +09:00
|
|
|
expect(out).to include("BUNDLER: Starting resolution")
|
2020-05-08 14:19:04 +09:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2018-11-02 23:07:56 +00:00
|
|
|
context "with ENV['DEBUG_RESOLVER'] set" do
|
|
|
|
it "produces debug output" do
|
|
|
|
gemfile <<-G
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "net_c"
|
|
|
|
gem "net_e"
|
|
|
|
G
|
|
|
|
|
2021-02-01 16:17:16 +01:00
|
|
|
bundle :install, :env => { "DEBUG_RESOLVER" => "1", "DEBUG" => "1" }
|
2018-11-02 23:07:56 +00:00
|
|
|
|
2020-12-15 08:32:54 +09:00
|
|
|
expect(out).to include("BUNDLER: Starting resolution")
|
2018-11-02 23:07:56 +00:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
context "with ENV['DEBUG_RESOLVER_TREE'] set" do
|
|
|
|
it "produces debug output" do
|
|
|
|
gemfile <<-G
|
2020-12-08 16:36:29 +09:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem "net_c"
|
|
|
|
gem "net_e"
|
|
|
|
G
|
|
|
|
|
2021-02-01 16:17:16 +01:00
|
|
|
bundle :install, :env => { "DEBUG_RESOLVER_TREE" => "1", "DEBUG" => "1" }
|
2018-11-02 23:07:56 +00:00
|
|
|
|
2021-02-01 16:17:16 +01:00
|
|
|
activated_groups = if local_platforms.any?
|
|
|
|
"net_b (1.0) (ruby), net_b (1.0) (#{local_platforms.join(", ")})"
|
|
|
|
else
|
|
|
|
"net_b (1.0) (ruby)"
|
|
|
|
end
|
2020-10-15 13:20:25 +09:00
|
|
|
|
2020-12-15 08:32:54 +09:00
|
|
|
expect(out).to include(" net_b").
|
2020-05-08 14:19:04 +09:00
|
|
|
and include("BUNDLER: Starting resolution").
|
|
|
|
and include("BUNDLER: Finished resolution").
|
2020-10-15 13:20:25 +09:00
|
|
|
and include("Attempting to activate [#{activated_groups}]")
|
2018-11-02 23:07:56 +00:00
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "when a required ruby version" do
|
|
|
|
context "allows only an older version" do
|
|
|
|
it "installs the older version" do
|
|
|
|
build_repo2 do
|
2020-12-08 16:36:29 +09:00
|
|
|
build_gem "rack", "1.2" do |s|
|
|
|
|
s.executables = "rackup"
|
|
|
|
end
|
|
|
|
|
2018-11-02 23:07:56 +00:00
|
|
|
build_gem "rack", "9001.0.0" do |s|
|
|
|
|
s.required_ruby_version = "> 9000"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2019-12-14 19:49:16 +09:00
|
|
|
install_gemfile <<-G, :artifice => "compact_index", :env => { "BUNDLER_SPEC_GEM_REPO" => gem_repo2.to_s }
|
2018-11-02 23:07:56 +00:00
|
|
|
ruby "#{RUBY_VERSION}"
|
|
|
|
source "http://localgemserver.test/"
|
|
|
|
gem 'rack'
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(out).to_not include("rack-9001.0.0 requires ruby version > 9000")
|
|
|
|
expect(the_bundle).to include_gems("rack 1.2")
|
|
|
|
end
|
2019-04-14 06:01:35 +00:00
|
|
|
|
|
|
|
it "installs the older version under rate limiting conditions" do
|
|
|
|
build_repo4 do
|
|
|
|
build_gem "rack", "9001.0.0" do |s|
|
|
|
|
s.required_ruby_version = "> 9000"
|
|
|
|
end
|
|
|
|
build_gem "rack", "1.2"
|
|
|
|
build_gem "foo1", "1.0"
|
|
|
|
end
|
|
|
|
|
2019-12-14 19:49:16 +09:00
|
|
|
install_gemfile <<-G, :artifice => "compact_index_rate_limited", :env => { "BUNDLER_SPEC_GEM_REPO" => gem_repo4.to_s }
|
2019-04-14 06:01:35 +00:00
|
|
|
ruby "#{RUBY_VERSION}"
|
|
|
|
source "http://localgemserver.test/"
|
|
|
|
gem 'rack'
|
|
|
|
gem 'foo1'
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(out).to_not include("rack-9001.0.0 requires ruby version > 9000")
|
|
|
|
expect(the_bundle).to include_gems("rack 1.2")
|
|
|
|
end
|
2020-05-08 14:19:04 +09:00
|
|
|
|
|
|
|
it "installs the older not platform specific version" do
|
|
|
|
build_repo4 do
|
|
|
|
build_gem "rack", "9001.0.0" do |s|
|
|
|
|
s.required_ruby_version = "> 9000"
|
|
|
|
end
|
|
|
|
build_gem "rack", "1.2" do |s|
|
|
|
|
s.platform = mingw
|
|
|
|
s.required_ruby_version = "> 9000"
|
|
|
|
end
|
|
|
|
build_gem "rack", "1.2"
|
|
|
|
end
|
|
|
|
|
|
|
|
simulate_platform mingw do
|
|
|
|
install_gemfile <<-G, :artifice => "compact_index", :env => { "BUNDLER_SPEC_GEM_REPO" => gem_repo4.to_s }
|
|
|
|
ruby "#{RUBY_VERSION}"
|
|
|
|
source "http://localgemserver.test/"
|
|
|
|
gem 'rack'
|
|
|
|
G
|
|
|
|
end
|
|
|
|
|
|
|
|
expect(out).to_not include("rack-9001.0.0 requires ruby version > 9000")
|
|
|
|
expect(out).to_not include("rack-1.2-#{Bundler.local_platform} requires ruby version > 9000")
|
|
|
|
expect(the_bundle).to include_gems("rack 1.2")
|
|
|
|
end
|
2018-11-02 23:07:56 +00:00
|
|
|
end
|
|
|
|
|
|
|
|
context "allows no gems" do
|
|
|
|
before do
|
|
|
|
build_repo2 do
|
|
|
|
build_gem "require_ruby" do |s|
|
|
|
|
s.required_ruby_version = "> 9000"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
let(:ruby_requirement) { %("#{RUBY_VERSION}") }
|
|
|
|
let(:error_message_requirement) { "~> #{RUBY_VERSION}.0" }
|
|
|
|
|
|
|
|
shared_examples_for "ruby version conflicts" do
|
|
|
|
it "raises an error during resolution" do
|
2020-05-08 14:19:04 +09:00
|
|
|
skip "ruby requirement includes platform and it shouldn't" if Gem.win_platform?
|
|
|
|
|
2020-06-03 18:43:17 +02:00
|
|
|
install_gemfile <<-G, :artifice => "compact_index", :env => { "BUNDLER_SPEC_GEM_REPO" => gem_repo2.to_s }, :raise_on_error => false
|
2018-11-02 23:07:56 +00:00
|
|
|
source "http://localgemserver.test/"
|
|
|
|
ruby #{ruby_requirement}
|
|
|
|
gem 'require_ruby'
|
|
|
|
G
|
|
|
|
|
|
|
|
expect(out).to_not include("Gem::InstallError: require_ruby requires Ruby version > 9000")
|
|
|
|
|
|
|
|
nice_error = strip_whitespace(<<-E).strip
|
2019-04-14 06:01:35 +00:00
|
|
|
Bundler found conflicting requirements for the Ruby\0 version:
|
2018-11-02 23:07:56 +00:00
|
|
|
In Gemfile:
|
2021-02-01 16:17:16 +01:00
|
|
|
Ruby\0 (#{error_message_requirement})
|
2018-11-02 23:07:56 +00:00
|
|
|
|
2021-02-01 16:17:16 +01:00
|
|
|
require_ruby was resolved to 1.0, which depends on
|
2019-04-14 06:01:35 +00:00
|
|
|
Ruby\0 (> 9000)
|
2018-11-02 23:07:56 +00:00
|
|
|
|
2019-04-14 06:01:35 +00:00
|
|
|
Ruby\0 (> 9000), which is required by gem 'require_ruby', is not available in the local ruby installation
|
2018-11-02 23:07:56 +00:00
|
|
|
E
|
2019-06-01 12:49:40 +03:00
|
|
|
expect(err).to end_with(nice_error)
|
2018-11-02 23:07:56 +00:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
it_behaves_like "ruby version conflicts"
|
|
|
|
|
|
|
|
describe "with a < requirement" do
|
|
|
|
let(:ruby_requirement) { %("< 5000") }
|
2020-10-15 13:20:25 +09:00
|
|
|
let(:error_message_requirement) { "< 5000" }
|
2018-11-02 23:07:56 +00:00
|
|
|
|
|
|
|
it_behaves_like "ruby version conflicts"
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "with a compound requirement" do
|
|
|
|
let(:reqs) { ["> 0.1", "< 5000"] }
|
|
|
|
let(:ruby_requirement) { reqs.map(&:dump).join(", ") }
|
2020-10-15 13:20:25 +09:00
|
|
|
let(:error_message_requirement) { Gem::Requirement.new(reqs).to_s }
|
2018-11-02 23:07:56 +00:00
|
|
|
|
|
|
|
it_behaves_like "ruby version conflicts"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
describe "when a required rubygems version disallows a gem" do
|
|
|
|
it "does not try to install those gems" do
|
|
|
|
build_repo2 do
|
|
|
|
build_gem "require_rubygems" do |s|
|
|
|
|
s.required_rubygems_version = "> 9000"
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2020-06-03 18:43:17 +02:00
|
|
|
install_gemfile <<-G, :raise_on_error => false
|
2019-05-06 18:06:21 +02:00
|
|
|
source "#{file_uri_for(gem_repo2)}"
|
2018-11-02 23:07:56 +00:00
|
|
|
gem 'require_rubygems'
|
|
|
|
G
|
|
|
|
|
2019-04-14 06:01:35 +00:00
|
|
|
expect(err).to_not include("Gem::InstallError: require_rubygems requires RubyGems version > 9000")
|
|
|
|
expect(err).to include("require_rubygems-1.0 requires rubygems version > 9000, which is incompatible with the current version, #{Gem::VERSION}")
|
2018-11-02 23:07:56 +00:00
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|