diff options
Diffstat (limited to 'lib/spack/docs/module_file_support.rst')
| -rw-r--r-- | lib/spack/docs/module_file_support.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/lib/spack/docs/module_file_support.rst b/lib/spack/docs/module_file_support.rst index 45f9f74376..5913434e04 100644 --- a/lib/spack/docs/module_file_support.rst +++ b/lib/spack/docs/module_file_support.rst @@ -308,7 +308,7 @@ the variable ``FOOBAR`` will be unset. spec constraints are instead evaluated top to bottom. """""""""""""""""""""""""""""""""""""""""""" -Blacklist or whitelist specific module files +Exclude or include specific module files """""""""""""""""""""""""""""""""""""""""""" You can use anonymous specs also to prevent module files from being written or @@ -322,8 +322,8 @@ your system. If you write a configuration file like: modules: default: tcl: - whitelist: ['gcc', 'llvm'] # Whitelist will have precedence over blacklist - blacklist: ['%gcc@4.4.7'] # Assuming gcc@4.4.7 is the system compiler + include: ['gcc', 'llvm'] # include will have precedence over exclude + exclude: ['%gcc@4.4.7'] # Assuming gcc@4.4.7 is the system compiler you will prevent the generation of module files for any package that is compiled with ``gcc@4.4.7``, with the only exception of any ``gcc`` @@ -490,7 +490,7 @@ satisfies a default, Spack will generate the module file in the appropriate path, and will generate a default symlink to the module file as well. -.. warning:: +.. warning:: If Spack is configured to generate multiple default packages in the same directory, the last modulefile to be generated will be the default module. @@ -589,7 +589,7 @@ Filter out environment modifications Modifications to certain environment variables in module files are there by default, for instance because they are generated by prefix inspections. If you want to prevent modifications to some environment variables, you can -do so by using the environment blacklist: +do so by using the ``exclude_env_vars``: .. code-block:: yaml @@ -599,7 +599,7 @@ do so by using the environment blacklist: all: filter: # Exclude changes to any of these variables - environment_blacklist: ['CPATH', 'LIBRARY_PATH'] + exclude_env_vars: ['CPATH', 'LIBRARY_PATH'] The configuration above will generate module files that will not contain modifications to either ``CPATH`` or ``LIBRARY_PATH``. |