We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature functionality I'm not 100% sure but I think we need to create a new spack recipe for every release.
Also, RELEASE.md needs to be updated with relevant instructions.
The text was updated successfully, but these errors were encountered:
I have contacted Sven (who was originally working on this) on this issue... may he knows more on how to keep versions up to date in spack
Sorry, something went wrong.
Let's get a couple lines of instructions from Sven, so next time we can update the recipe ourselves right after a release, what do you think @mrfh92 ?
As far as I understand, one has to create a new PR in the spack repo and to manually add the new version and its dependencies: spack/spack#44835
This issue is stale because it has been open for 60 days with no activity.
No branches or pull requests
Feature functionality
I'm not 100% sure but I think we need to create a new spack recipe for every release.
Also, RELEASE.md needs to be updated with relevant instructions.
The text was updated successfully, but these errors were encountered: