Open
Conversation
Replace obsolete "spack concretize -U" with spack:concretizer:reuse:false to disable it by default within our build environment. Move compiler definitions from compilers.yaml to packages.yaml since compilers.yaml is obsolete in v1.0 Update specs to handle new semantics for "%" in v1.0 Updated using packages to point to new, separate package repository for spack. Added "depends_on" for package language dependencies (c, cxx, fortran) Renamed "m-aneos" package to "m_aneos" to match new package naming requirements of spack v1.0
This comment was marked as outdated.
This comment was marked as outdated.
…, added c and cxx dependencies for packages missing them, added fortran dependency to spheral to avoid known spack bug, python concretize function is called instead of SpackCommand
mcfadden8
commented
Oct 27, 2025
mcfadden8
commented
Oct 27, 2025
mcfadden8
commented
Oct 27, 2025
…or tpl-manager.py
becker33
reviewed
Oct 30, 2025
Member
becker33
left a comment
becker33
left a comment
There was a problem hiding this comment.
Commeting everything I noticed while looking for the issue we were discussing on slack for setting the working dir.
…o package names are maintained by spack
mcfadden8
commented
Feb 17, 2026
- use raja@2025.9.1 - use chai@2025.09.0 - add version SHA for polytope v0.7.5
mcfadden8
force-pushed
the
task/spack1.0.2
branch
from
222fa74 to
4d40fe8
Compare
Spack has been decoupled from the packages it manages in v1 allowing for more than just spack to be installed as part of a "spack instance". The tpl-manager.py now allows for the user to specify a directory where the spack instance, the package instance, as well as some other miscellaneous items.
mcfadden8
commented
Feb 19, 2026
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v3 | ||
| uses: actions/checkout@v4 |
Collaborator
Author
There was a problem hiding this comment.
In case anyone is curious about this change, I had some problems when/if PolyClipper was being checked out. Updating to v4 and including the tokens for recursive checkout fixed it.
'extern/PolyClipper'...
...
'extern/PYB11Generator/extern/pybind11'
Cloning into '/home/runner/work/spheral/spheral/extern/PYB11Generator/extern/pybind11'...
Error: fatal: could not read Username for 'https://github.com': terminal prompts disabled
Collaborator
|
Need to update the RELEASE_NOTES.md. |
… buildcache scripts
Also, add option to allow user to set the debug output level for spack should one run into a problem with spack.
…n installing from a buildcache
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
3 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.
Summary
ToDo :
RELEASE_NOTES.mdwith notable changes.