... | @@ -45,7 +45,7 @@ An overlay is defined by the two root directories. Different names can be used f |
... | @@ -45,7 +45,7 @@ An overlay is defined by the two root directories. Different names can be used f |
|
|
|
|
|
If only the root directory for the software installation is specified, this is also used as root for the modulefiles.
|
|
If only the root directory for the software installation is specified, this is also used as root for the modulefiles.
|
|
|
|
|
|
==== Configuration files
|
|
==== Overlay definition files
|
|
|
|
|
|
Configuration files are in YAML format.
|
|
Configuration files are in YAML format.
|
|
|
|
|
... | @@ -112,4 +112,30 @@ Note: the Git module from the base overlay is not available any more. |
... | @@ -112,4 +112,30 @@ Note: the Git module from the base overlay is not available any more. |
|
With the implementation of overlays a new format for the so called variant files is necessary. In the old format extensions are almost impossible. Nowadays a common format used for configuration files is YAML.
|
|
With the implementation of overlays a new format for the so called variant files is necessary. In the old format extensions are almost impossible. Nowadays a common format used for configuration files is YAML.
|
|
|
|
|
|
==== YAML format of variant files
|
|
==== YAML format of variant files
|
|
TBW |
|
----
|
|
\ No newline at end of file |
|
---
|
|
|
|
overlay: <overlay-name>
|
|
|
|
module_name/module_version:
|
|
|
|
variants:
|
|
|
|
- relstage: <release-stage>
|
|
|
|
modulefiles_root_dir: <modulefile-root-dir>
|
|
|
|
dependencies:
|
|
|
|
- dependency_1
|
|
|
|
- dependency_2
|
|
|
|
- ...
|
|
|
|
...
|
|
|
|
----
|
|
|
|
`overlay`:: Name of the overlay the module will be installed in. The specified overlay must be defined in one of the overlay definition files. If no overlay is specified the base overlay is used.
|
|
|
|
|
|
|
|
`module_name/module_version`:: Specification of the module with this name and version. For each version a specification should be added.
|
|
|
|
|
|
|
|
`variants`:: Array of variants.
|
|
|
|
|
|
|
|
`relstage`:: Release stage, either `unstable`, `stable` or `deprecated`. If not specified the release stage defaults to `unstable`.
|
|
|
|
|
|
|
|
`modulefiles_root_dir`:: This key can be used to overwrite the `modulefiles_root_dir` specified in the overlay definition file.
|
|
|
|
|
|
|
|
`dependencies`:: Array of dependencies. Dependencies can have one of the following prefixes:
|
|
|
|
+
|
|
|
|
* `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. An 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. |
|
|
|
\ No newline at end of file |