Fix rubygems update when non default --install-dir
is configured
#5566
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the end-user or developer problem that led to this PR?
If RubyGems is configured with a non default
--install-dir
,gem update --system
will fail because it tries to switching to therubygems-update
installation folder in the default gem dir, and the gem is not there.What is your fix for the problem, implemented in this PR?
Use
spec.base_dir
of the installed updater gem, instead of always usingGem.dir
.Fixes #5541.
Make sure the following tasks are checked