Skip to content
New issue

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

Revise "with when" ranges in MOM5 Spack package #182

Closed
penguian opened this issue Jan 8, 2025 · 3 comments
Closed

Revise "with when" ranges in MOM5 Spack package #182

penguian opened this issue Jan 8, 2025 · 3 comments
Assignees

Comments

@penguian
Copy link
Contributor

penguian commented Jan 8, 2025

At https://github.com/ACCESS-NRI/spack-packages/blob/main/packages/mom5/package.py there is an "access-esm1.6" version that uses the "master" branch. The second with when uses the inclusive range "@access-esm1.5:access-esm1.6" so version @access-esm1.6 would match the second with when. The first with when uses the range "@:access-esm0,access-esm2:" which matches the preferred @master version. So building mom5@master builds from the same mom5 branch as building mom5@access-esm1.6 but uses a different set of dependencies.

This is wrong. Either we should change the ranges to "@access-esm1.5" and "@:access-esm0,access-esm1.6:" or we should remove the "access-esm1.6" version, or both.

@harshula
Copy link
Collaborator

harshula commented Jan 8, 2025

Hi @penguian , IIRC, a MOM5 build for ESM 1.6 does not depend on libaccessom2, so the behaviour you described may be intentional.

The type variant definition should be double checked. Should we have?:

conditional("ACCESS-OM", "ACCESS-OM-BGC", "MOM_solo", when="@:access-esm0,access-esm2:")

@penguian penguian self-assigned this Jan 16, 2025
@dougiesquire
Copy link
Contributor

Yup, the current behaviour is intentional - see ACCESS-NRI/MOM5#25

@penguian
Copy link
Contributor Author

Closing due to previous comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants