mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
d0bf31e6cf
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 |
||
|---|---|---|
| .. | ||
| bundler | ||
| cache | ||
| commands | ||
| install | ||
| lock | ||
| other | ||
| plugins | ||
| realworld | ||
| resolver | ||
| runtime | ||
| support | ||
| update | ||
| quality_es_spec.rb | ||
| quality_spec.rb | ||
| spec_helper.rb | ||