Rakudo home env precedence #3797
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So one can still influence the Rakudo home even with non-relocatable Rakudo builds. This fixes rakudo#2815
vrurg
approved these changes
Jul 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The precedence of the different RAKUDO_HOME sources was wrong. A static rakudo home set by Configure in every non-relocatable build was most dominant and thus couldn't be overridden with an environment variable anymore. That makes little sense. It also broke spec tests using Inline-Perl5 using the build runners, because the build runner relies on the RAKUDO_HOME env variable to set a different rakudo home.
This fixes #2815.