Answer A-480: a held module still provides what its running build provides
This commit is contained in:
@@ -1907,3 +1907,10 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
keep what a module holds safe; they never hold a want for another module's delivery or for the build an acting part
|
||||
runs, which is what A-478 ends. "The assigner's whole want rule" in A-478 is the rule that chooses the version; the
|
||||
order waits choose only when, on that machine, the want's apply goes. (From the review of A-478.)
|
||||
- **A-480** (A-426a for the node-engine; A-461d; principles 2, 3 and 7) A module the node holds keeps running what it
|
||||
runs, and so keeps providing what that running build provides: the composer counts it as the provider of each
|
||||
provision its running build's manifest provides (from the composition it runs on this node), whatever its version
|
||||
and whether or not the catalog lists that build. A held provider never makes a module that requires it "nothing
|
||||
provides"; only a provision no running or composable module provides does. The hold of the provider is still said
|
||||
as its own. (Live, 2026-11-17 22:52: g14 held feh 0.1.8 for "nothing provides \"x11-display\", wanted by feh" while
|
||||
xorg runs on g14, held only because the catalog holds no entry of its running build.)
|
||||
|
||||
Reference in New Issue
Block a user