Fix some warnings during bin/rake spec:deps
#3986
Merged
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 have multiple versions of
mustache
orrdiscount
installed on your system and you runbin/rake spec:deps
from the root of thebundler
folder, you'll get warnings like this:The explanation is that loading the
Rakefile
requiresronn
for loading the man pages tasks.rdiscount
andmustache
are dependencies ofronn
, but since there are multiple versions of them on the system, they are left unresolved until they are eventually required. However, duringbin/rake spec:deps
,bundler
will change the rubygems environment to prepare for the specs and eventually callsGem::Specification.reset
to apply new gem paths. Since these gems are unresolved at that time, a warning is printed.What is your fix for the problem, implemented in this PR?
The solution is to lazily require ronn only when man pages tasks are actually run.
This commit is best viewed ignoring whitespace changes.
Tasks:
I will abide by the code of conduct.