aboutsummaryrefslogtreecommitdiffstats
path: root/lib/rubygems.rb
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2024-01-11 21:53:26 +0100
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2024-01-19 11:28:11 +0900
commitf1f5f22d22a149f20e019728b1ab35593d29d81a (patch)
tree2007719038a6c427f1142d01914404f46a6ea670 /lib/rubygems.rb
parent8044e57907bc5a066ca9ef309d90c62906f8e2ec (diff)
downloadruby-f1f5f22d22a149f20e019728b1ab35593d29d81a.tar.gz
[rubygems/rubygems] Fix `require` of a default gem when unresolved gems depend on it
The following conditions must be met: * A default gem is required. * A previous require left some gems unresolved, and those dependencies themselves depend on the default gem. In this case, rubygems require will first activate the default version of the gem, then try to activate another unresolved version of the default gem that conflicts with the first activation. The solution is, if we are in the middle of requiring a default gem, skip this step, because we have already activated it successfully. https://github.com/rubygems/rubygems/commit/8cd5608db5 Co-authored-by: Stan Hu <stanhu@gmail.com>
Diffstat (limited to 'lib/rubygems.rb')
0 files changed, 0 insertions, 0 deletions