This repository has been archived on 2026-11-02. You can view files and clone it. You cannot open issues or pull requests or push a commit.

jschoubben cfe2816495 A module names the module its build stands on, not a copy of it ...

A fingerprint written into a recipe names one particular copy of the base — the
copy on whichever machine the person typing it was using. On any other mesh that
copy has never existed, so the build stops on its first line with a message
about an image nobody can look up. Three modules in the catalogue were in
exactly that state, and the line each of them replaced was equally dead.

A module now names the module and artifact instead, and the mesh answers with
what it holds. The builder is still a thing that clones, builds and answers: the
answer travels with the question, because only the mesh knows what it has.

A base the mesh has not built is refused before anything is built, naming which
module has to exist first.

2026-09-13 23:53:22 +02:00

..

mesh-builder

A module names the module its build stands on, not a copy of it

2026-09-13 23:53:22 +02:00

mesh-control

A module names the module its build stands on, not a copy of it

2026-09-13 23:53:22 +02:00