Fix bundle plugin install
detection of already installed plugins
#4869
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 you install a version of a plugin, say diffend 0.2.49, and then the latest version, 0.2.50,
bundler
will incorrectly think that 0.2.50 is already installed, and skip installation.What is your fix for the problem, implemented in this PR?
Plugins are regular gems, but they are installed to their own
GEM_HOME
. My fix is to set the properGEM_HOME
used for plugins, so that the detection of whether a specific version is already installed works in the same way it works for regular gems.Fixes #4864 (comment).
Make sure the following tasks are checked