Allow rebuilding the module tree via some envvars#100
Conversation
|
Some example usages: |
|
|
||
| echo ">> Checking for EasyBuild module..." | ||
| REQ_EB_VERSION='4.3.4' | ||
| echo ">> Checking for EasyBuild module (required version is ${REQ_EB_VERSION})..." |
There was a problem hiding this comment.
To be honest, since a specific version is required we should be trying to load that version, not the default. If we fail, we should get eb to install the latest release, and if that is too recent use the latest version to install the required version.
There was a problem hiding this comment.
We can do that in this block with module avail easybuild/${REQ_EB_VERSION}, then using a temporary pip installation to either give us the required version or the latest release if that is not available.
There was a problem hiding this comment.
@bedroge You are right, I will fix this and use module show instead
Be more specific about what version of eb we check for and install
… into rebuild_module_tree
| module avail 2>&1 | grep -i easybuild/${REQ_EB_VERSION} &> ${ml_av_easybuild_out} | ||
| echo ">> Checking for ${EB_MODULE_NAME} module (required version is ${REQ_EB_VERSION})..." | ||
| ml_show_easybuild_out=$TMPDIR/ml_show_easybuild.out | ||
| module show ${EB_MODULE_NAME}/${REQ_EB_VERSION} &> ${ml_show_easybuild_out} |
|
I think I would like to change where we install modules to actually use the naming scheme in the path, so |
add OpenSSL/1.1 to NESSI/2023.04
|
@ocaisa Is this still relevant? I've just introduced |
|
@boegel Yes, still relevant but requires yet another update at this point. |
|
Closing this, can return to it at some point |
3 participants
Fixes #89
Requires
easybuilders/easybuild-framework#3659to work