Answer A-482: a running build is one the node's own record says runs
This commit is contained in:
@@ -1935,3 +1935,10 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
resolve that holds each built artifact's texts), and read by the node-engine's parts check; one change across those
|
||||
repositories. (From the develop of A-481: the composition's layout is the seat's strict wire type, and no field of
|
||||
it fits.)
|
||||
- **A-482** (A-480a; principles 2 and 3) "A held module's running build" is one this node's own record says runs: the
|
||||
module is heard running here, is in what the agent runs, or its have names a build in the phase running or held (a
|
||||
held module keeps running what it runs). A module wanted here with none of these is not running, whatever it was
|
||||
heard of: its trunk build is not laid for it, and what only it would provide stays "nothing provides". (From the
|
||||
review of the heard-running change: it counted every wanted module not heard stopped, so a module placed here that
|
||||
never ran provided what it does not run. Live, g14: xorg runs from a build placed by hand, said by no running event,
|
||||
and its have says running at that build.)
|
||||
|
||||
Reference in New Issue
Block a user