-
Notifications
You must be signed in to change notification settings - Fork 17
Add a top-lever dir init/modules/EESSI
containing a symlink to the 2023.06 modulefile
#198
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
base: main
Are you sure you want to change the base?
Conversation
modules/EESSI
containing a symlink to the 2023.06 modulefileinit/modules/EESSI
containing a symlink to the 2023.06 modulefile
@bedroge I was checking how we populated |
Yes, I think that's correct, though I did publish the thing in the end. So would be good to still merge this. |
For EESSI 2025.06, we want to create a symlink as well, and (for now) an additional -- hide EESSI/2025.06 module until software layer has enough installations in it
hide_version("EESSI/2025.06") |
…ESSI/2205.06 for now
@bedroge This will need to be done to start building out software layer for EESSI 2025.06, since the So I took a stab at it (totally untested): bedroge#4 |
also symlink `init/modules/EESSI/2025.06.lua` + add `.modulerc` to hide `EESSI/2205.06` for now
This needs EESSI/software-layer-scripts#6 to be merged first. |
…_modulefile_symlink
Tested this by running the playbook and without publishing the transaction:
Looks good to me. The |
Gave it a try in a container, apparently the
So I changed that in the vars file. |
Tested it in a transaction that I aborted/didn't publish, this is the result: