Files
mesh-catalog/modules/go/README.md
T
mesh-tools ceb42b0e92
mesh/merge-gate head ceb42b0e920e merged into trunk 5efd84e93e38 — pass: builds new: modules/go, modules/nodejs, sent nowhere; no bus step; every machine c…
mesh/repo-check head ceb42b0e920e merged into trunk 5efd84e93e38 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/delivery delivered
Say in the go and nodejs READMEs what holds at this step, and what holds once the users require them (review of issue 1573 step A)
2026-10-21 09:25:23 +00:00

15 lines
872 B
Markdown

# go
The Go toolchain as a module (novox/hq ADR 0477 §4, issue 1573).
- **Declares the package `go`.** Today dev-tools, lab and mesh-build-go declare it too, which the resolver allows
(ADR 0303); once they require `go-toolchain` instead (issue 1573's second step), this is the only module that
declares it, and `checks/toolchains` refuses another.
- **Provides `go-toolchain` with the machine's reach**: a module that requires it composes only on a machine where
this module is assigned. It is never pulled in for whatever asked, so `go` is assigned to a node on purpose.
Nothing requires it yet; dev-tools, lab and mesh-build-go will, in the second step.
- Holds no long-running resource, so it adds nothing to `health-undeclared`.
The node-engine never uninstalls a package, so when the users stop declaring `go`, nothing leaves a node that has
this module.