envmodules/modules
1
0
Fork 0
mirror of https://github.com/envmodules/modules.git synced 2026-06-14 00:42:43 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: desc. not-found depre reload skip in man/NEWS

Browse Source 
Signed-off-by: Xavier Delaruelle <xavier.delaruelle@cea.fr>
This commit is contained in:
Xavier Delaruelle
2025-06-04 07:03:09 +02:00
parent 5e48ddf46e
commit 4c2da53732
2 changed files with 16 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
NEWS.rst
View File

@@ -162,6 +162,10 @@ Modules 5.6.0 (not yet released)
* Install: installation option :instopt:`--enable-new-features` is updated to
include :instopt:`--enable-require-via`.
* Doc: add :ref:`require-via` design notes.
* Skip reload of a *Dependent Reload* module if it is not found after a change
in enabled modulepaths. Reload of a not found module is attempted only if it
is tagged *super-sticky* or *sticky* and force mode is disabled. Skipped
module is considered *Dependent Unload* module.
.. _Security policy: https://github.com/envmodules/modules/blob/main/SECURITY.md
.. _Modules chat room: https://matrix.to/#/#modules:matrix.org

18
doc/source/module.rst
View File

@@ -4500,12 +4500,18 @@ ENVIRONMENT
evaluation of the main *modulefile* (either load, unload or switch
evaluation).
The reload phase of a Dependent Reload modulefile is skipped either if the
requirements of this modulefile are not loaded or if a conflict is spotted
with the loaded environment. Reload is attempted in any case if modulefile is
tagged ``super-sticky`` or ``sticky`` and force mode is disabled. Dependent
Reload module whose reload has been skipped are considered Dependent Unload
module.
The reload phase of a Dependent Reload modulefile is skipped if any of the
following conditions are met:
* The required modules for this modulefile are not loaded.
* A conflict is detected with the currently loaded environment.
* The enabled modulepaths have changed, and the modulefile is no longer
available.
However, reload is always attempted if the modulefile is tagged as
``super-sticky`` or ``sticky``, and force mode is not enabled. Dependent
Reload modulefiles whose reload has been skipped are treated as Dependent
Unload modulefiles.
Conflict Unload mechanism is activated only if :mconfig:`conflict_unload`
configuration option is also enabled.