... | ... | @@ -61,11 +61,12 @@ The user configuration file is queried first and can be used to overwrite the de |
|
|
Format:
|
|
|
----
|
|
|
---
|
|
|
name_of_overlay:
|
|
|
root_dir: <DIR>
|
|
|
modulefiles_root_dir: <DIR>
|
|
|
type: normal|hidding|replacing
|
|
|
...
|
|
|
overlays:
|
|
|
name_of_overlay:
|
|
|
root_dir: <DIR>
|
|
|
modulefiles_root_dir: <DIR>
|
|
|
type: normal|hidding|replacing
|
|
|
...
|
|
|
----
|
|
|
|
|
|
`name_of_overlay`:: Is the name of the overlay.
|
... | ... | @@ -86,7 +87,7 @@ Example: Assume we have the overlays `base` and `private`. In the base overlay a |
|
|
After loading the private overlay the following Gnuplot modules are available:
|
|
|
+
|
|
|
* `git/2.33.1`and `gnuplot/5.4.0` from the base overlay
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3`from the private overlay
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3` from the private overlay
|
|
|
+
|
|
|
Note: the module `gnuplot/5.4.2` from the base overlay has been replaced by the module with the same name from the private overlay.
|
|
|
|
... | ... | @@ -97,7 +98,7 @@ Example: Assume we have the same overlays and Gnuplot modules as in the example |
|
|
After loading the private overlay with type `hiding` the following Gnuplot modules are available:
|
|
|
+
|
|
|
* `git/2.33.1` from the base overlay
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3`from the private overlay
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3` from the private overlay
|
|
|
+
|
|
|
Note: the Gnuplot modules from the base overlay are hidden!
|
|
|
|
... | ... | @@ -105,7 +106,7 @@ Note: the Gnuplot modules from the base overlay are hidden! |
|
|
+
|
|
|
Example: If you load the private overlay from the examples above as replacing, the following modules are available in the group `Tools`:
|
|
|
+
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3`from the private overlay
|
|
|
* `gnuplot/5.4.2` and `gnuplot/5.4.3` from the private overlay
|
|
|
+
|
|
|
Note: the Git module from the base overlay is not available any more.
|
|
|
|
... | ... | @@ -115,11 +116,13 @@ With the implementation of overlays a new format for the so called variant files |
|
|
==== YAML format of variant files
|
|
|
----
|
|
|
---
|
|
|
overlay: <overlay-name>
|
|
|
defaults:
|
|
|
overlay: <overlay-name>
|
|
|
module_name/module_version:
|
|
|
variants:
|
|
|
- relstage: <release-stage>
|
|
|
modulefiles_root_dir: <modulefile-root-dir>
|
|
|
use_flags: <flags>
|
|
|
overlay: <overlay-name>
|
|
|
dependencies:
|
|
|
- dependency_1
|
|
|
- dependency_2
|
... | ... | @@ -140,4 +143,7 @@ module_name/module_version: |
|
|
+
|
|
|
* `b:` build-dependency: A build-dependency is required at build time and must be loaded to compile the module. But it is not required at runtime.
|
|
|
* `i:` install-dependency: A install-dependency is required at runtime, but must not be loaded at runtime of the module. An example is the Intel compiler. It requires GCC but GCC must not be loaded. A install-dependency is loaded at build-time.
|
|
|
* no prefix: dependencies without prefix must be loaded at build- and runtime. |
|
|
\ No newline at end of file |
|
|
* no prefix: dependencies without prefix must be loaded at build- and runtime.
|
|
|
|
|
|
==== Variants file and overlays
|
|
|
|