Make MCORE_LIBS prioritize earlier entries #959
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.
This change makes the
MCORE_LIBSenvironment variable behave a touch more like similar variables for other languages (orPATH): earlier entries are prioritized over later ones. Previously the behavior was the opposite.This is relevant for the self-contained version of TreePPL (see treeppl/treeppl-python#9), which adds its own versions of the various libraries to
MCORE_LIBSbefore starting. Potential options for how to get the desired behavior there include:MCORE_LIBSin the users environment, remove entries forstdlib,coreppl, andtreeppl, then add the correct ones. This removes duplicates, but is fiddly to get right inbash.I would prefer the last option (hence this PR), since it's the most consistent with the rest of the world, and it shouldn't affect any normal setups.