novox/mesh-controller
12
0
Fork 0
Code Issues Pull Requests 5 Releases Wiki Activity

catalogue: say in the comments that a package may be declared by several modules (issue 628)
mesh/merge-gate head b654b320a18a merged into trunk 584aa2d7d7a5 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Details
mesh/repo-check head b654b320a18a merged into trunk 584aa2d7d7a5 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details

Browse Source 
The resolver follows ADR 0303, but four comments still stated ADR 0210's retired rule that two modules declaring one package collide, and an agent took them as the rule. What stays exclusive is what a module owns: a path, a unit, a name, and a package declared present by one module and absent by another.
This commit is contained in:
mesh-admin
2026-10-13 11:52:17 +00:00
parent 584aa2d7d7
commit b654b320a1
4 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
internal/catalogue/generated_collision_test.go
+2 -1
View File
@@ -6,7 +6,8 @@ import (
)
// novox/hq issue 190, step 5 (ADR 0222): what the mesh computes for a module is held to the rule
// every module is — no two modules on a machine declare one path, unit, name or package. The
// every module is — no two modules on a machine declare one path, unit or name (a package may be declared by
// several, novox/hq ADR 0303). The
// private network once declared the container runtime's file and service beside the runtime's own
// module, and nothing refused it, because the collision check only ever saw catalogue manifests.