Spackage changes need to be propagated to Spack upstream
Open
@rbberger is already working on this.
Since Oct 17, 2023.
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
Creating this more as a TODO for myself. The recent spackage changes introduce new variants that need to be propagated to Spack upstream.
New variants need to be added, conditionally based on a new version, and no longer existing variants need to be disabled for newer versions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.