Spack v1 Migration: Reserved Definitions Schema Update#60
Merged
Conversation
github-project-automation
bot
moved this to New Issues 🌅
in Spack `0.22` to `1.0` Migration
github-project-automation
bot
moved this from Review 👏
to Done ✅
in Spack `0.22` to `1.0` Migration
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
References ACCESS-NRI/build-cd#330, ACCESS-NRI/build-cd#332
Background
Since we are using the reserved spack definitions
_nameand_versionto inform deployment information, we can relax the constraints onspack.specs, which is good.The PR
The diff between 1-0-7 and 2-0-0 can be found in this commit: 1784be4