Always rely on $LOAD_PATH
when jumping from exe/
to lib/
#6702
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?
Normally, we use
require_relative
when requiring internal code. However, Bundler may also load external code (for example, bundler plugins), and when that external code loads Bundler itself, usingrequire_relative
without setting up the$LOAD_PATH
may lead into double load errors.For example, when testing a Gemfile using plugins using our source code tree, I get the following:
What is your fix for the problem, implemented in this PR?
Changing
exe/bundle
to always use$LOAD_PATH
.Make sure the following tasks are checked