I am releasing Lmod 8.1. This is mostly a bug fix release of Lmod over 8.0. It does include the "Extended Default" mechanism that was released in 8.0.7. Sites that run a non-hierarchical module layout may wish to disable the Extended Default mechanism.
As I pointed out when I released 8.0.7, this feature is to make it easier to deal with naming conventions where the version string is long. For example assume that a site has multiple versions of the intel compiler where intel/18.0.3 is the default.
intel/16.0.3
intel/17.0.1
intel/17.0.2
intel/18.0.1
intel/18.0.3 (D)
intel/18.0.4
Then:
$ module load intel/16 # => loads intel/16.0.3
$ module load intel/17 # => loads intel/17.0.2
$ module load intel/18 # => load intel/18.0.3
$ module load intel # => load intel/18.0.3
The idea is that the intel/16 picks the "best" intel/16.* and intel/17 picks the best 17.* The last two cases the best 18 version is the default (namely 18.0.3)
The lmod.sf.net<http://lmod.sf.net> site has a tar ball of Lmod 8.1 and the Lmod logos and as always github.com/TACC/Lmod<http://github.com/TACC/Lmod> has the latest version.
Best,
Robert.
--
Robert McLay, Ph.D.
Manager of Sottware Tools, HPC @ TACC
mc...@ta...<mailto:mc...@ta...>
|