Reintroduce icon-exclaim to spack-c2sm

[huppd]

• add package for ghex
• add package for hwmalloc
• add package for icon-exclaim
• add package for oomph
• add package for uv

[github-actions]

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2025-11-28 12:47 UTC

[msimberg]

This is an optional request, but for testing of NCCL for halo exchanges it'd be very nice to have up-to-date versions of nccl, aws-ofi-nccl, and libfabric. The latest versions are all available on the new spack-packages repo, but are of course not here on the old version of spack.

I suspect that it's maybe better to leave updating these out of this PR so as not to block it further? But for planning is here or in https://github.com/C2SM/software-stack-recipes the better place to put such updated package recipes? This could possibly be added as part of C2SM/software-stack-recipes#33.

[huppd]

This is an optional request, but for testing of NCCL for halo exchanges it'd be very nice to have up-to-date versions of nccl, aws-ofi-nccl, and libfabric. The latest versions are all available on the new spack-packages repo, but are of course not here on the old version of spack.

I suspect that it's maybe better to leave updating these out of this PR so as not to block it further? But for planning is here or in https://github.com/C2SM/software-stack-recipes the better place to put such updated package recipes? This could possibly be added as part of C2SM/software-stack-recipes#33.

I would keep these out of this MR just to keep the history clean. But for where is the best place to put them, I think for playing around this is the better place, but hopefully we can kind of converge to the spack main repo.

[msimberg]

This is an optional request, but for testing of NCCL for halo exchanges it'd be very nice to have up-to-date versions of nccl, aws-ofi-nccl, and libfabric. The latest versions are all available on the new spack-packages repo, but are of course not here on the old version of spack.
I suspect that it's maybe better to leave updating these out of this PR so as not to block it further? But for planning is here or in https://github.com/C2SM/software-stack-recipes the better place to put such updated package recipes? This could possibly be added as part of C2SM/software-stack-recipes#33.

I would keep these out of this MR just to keep the history clean. But for where is the best place to put them, I think for playing around this is the better place, but hopefully we can kind of converge to the spack main repo.

Yep, absolutely. Thanks for the response. I found out about the plans to move to spack 1.0 (which would bring newer packages) in the near future which would cover this use case. Until then I'm attempting to build a slimmer new icon uenv (only dependencies) based on a newer spack 1.0 stack which would cover my testing needs for now.

[huppd]

Thanks for the valuable feedback @msimberg and @havogt I hope I addressed them all now.

[msimberg]

Just a minor comment, but I'm picking nits. This looks good to me as it is.

[AnnikaLau]

cscs-ci run santis

[AnnikaLau]

cscs-ci run

[huppd]

cscs-ci run

[huppd]

cscs-ci run

[huppd]

cscs-ci run

[huppd]

launch jenkins

[huppd]

launch jenkins

[huppd]

launch jenkins

[huppd]

cscs-ci run

[huppd]

launch jenkins