Conversation
38b9aa1 to
66517d9
Compare
| require: "@git.1ed0669c57f041baa1f1070693991c3a7a43e7ee=develop" | ||
|
|
||
| # v2024.07.0 | ||
| # v2025.0.3.0 |
There was a problem hiding this comment.
can we specify this in the geos package instead of specifying a commit hash here? seems easier and does not require duplication.
There was a problem hiding this comment.
can we specify this in the geos package instead of specifying a commit hash here? seems easier and does not require duplication
As of a few days ago, yes: https://github.com/spack/spack/blame/8885f6b861ea8721711ad7d9030593968a62e959/var/spack/repos/builtin/packages/raja/package.py#L34-L39
Before that spack commit, v2025.03.0 was not in spack yet, so I went with the commit hash.
However, this involves updating our spack version to a newer commit, which may cause other issues.
I think it makes sense to get the v2025.03.0 changes in this PR in first, then do the refactoring and spack version bump in #305.
This PR:
setupLC-TPL-uberenv-helper.bashto remove extra build files on successful completion to avoid hitting directory size limit.GEOS-DEV/GEOS#3613
GEOS-DEV/LvArray#347