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

Feature request: Allow module version selection #64

Open
finnerty-fzj opened this issue Aug 31, 2023 · 0 comments
Open

Feature request: Allow module version selection #64

finnerty-fzj opened this issue Aug 31, 2023 · 0 comments

Comments

@finnerty-fzj
Copy link

Tcl environment modules use a .version file to specify the default version to load amongst a set of versions. It would be good to be able to be able to generate such files as this would make this tool more usable for shared deployments.
The modules file tree is something like.

- ${PACKAGE}/
     - .version
     - ${VERSION}/
         - .version
         - ${VARIANT}

Where the .version file contains the version to use when users load a tool without giving a version number. The following example makes 3.3 the default NEST (assuming only one module file or a .version file in the ${VERSION} sub-folder).

#%Module1.0
## Default NEST version
set ModulesVersion 3.3

Perhaps have shell variables in the plan files, like the following, that create the version files if they are set otherwise do nothing. This would require some decisions about what to do if multiple plan files have these set.

MODULES_DEFAULT_VERSION=...
MODULES_DEFAULT_VARIANT=...

Alternatively these could be created in an optional separate step like

    build.sh set_module_default_versions [package] [version] [variant:-default]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant