Make spack config:deprecated configuration accessible in environment
#153
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
albestro
force-pushed
the
config_deprecated
branch
from
5968f3f to
8de18f1
Compare
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.
Sometimes there's no other way than dealing with deprecated packages. Spack by default does not allow anymore to fetch packages version marked as deprecated, but it still keeps the door open for such edge cases allowing to control the behavior via
config:deprecated.This PR exposes this option in
environments.yamlkeeping the default spack behavior (i.e.false= don't allow to install deprecated versions).I didn't had the chance to fully test it, yet. In case this work is in the right direction, I will take care of updating the related documentation too before merging this PR.