1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
ruby--ruby/spec/bundler/realworld
David Rodríguez d0bf31e6cf [rubygems/rubygems] Don't on gemspecs with invalid require_paths, just warn
These gemspecs already work most of the times. When they are installed
normally, the require_paths in the gemspec stub line becomes actually
correct, and the incorrect value in the real gemspec is ignored. It only
becomes an issue in standalone mode.

In Ruby 3.2, `Kernel#=~` has been removed, and that means that it
becomes harder for us to gracefully deal with this error in standalone
mode, because it now happens earlier due to calling `Array#=~` for this
invalid gemspec (since require_paths is incorrectly an array of arrays).

The easiest way to fix this is to actually make this just work instead
by automatically fixing the issue when reading the packaged gemspec.

https://github.com/rubygems/rubygems/commit/d3f2fe6d26
2022-06-12 02:02:20 +09:00
..
fixtures/warbler Track RubyGems 3.4.0dev and Bundler 2.4.0dev 2021-12-27 10:45:36 +09:00
dependency_api_spec.rb
double_check_spec.rb
edgecases_spec.rb [rubygems/rubygems] Don't on gemspecs with invalid require_paths, just warn 2022-06-12 02:02:20 +09:00
ffi_spec.rb [rubygems/rubygems] Don't replace ENV twice on non Windows platforms 2021-11-25 04:02:19 +09:00
gemfile_source_header_spec.rb
mirror_probe_spec.rb Merge RubyGems-3.3.1 and Bundler-2.3.1 2021-12-23 09:44:45 +09:00
parallel_spec.rb Merge RubyGems and Bundler master 2022-02-28 11:39:20 +09:00
slow_perf_spec.rb [rubygems/rubygems] Relax performance spec limit 2022-06-07 21:04:53 +09:00