You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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).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.
Alternatively these could be created in an optional separate step like
The text was updated successfully, but these errors were encountered: