Design 47 H: H-A-202, the entry's form stays; the build module derives the same-repository tree
This commit is contained in:
@@ -1079,3 +1079,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
refuses (H-A-192). The indexer pins, in the entry's `packages`, every mesh package the module's build requires at
|
||||
the zero version, transitively across the module graph it reads from the go.mod files (H-A-157), not only the direct
|
||||
requirements; a same-repository requirement is built from the tree (H-A-198). P4 (the indexer owns the entry), P7.
|
||||
- **H-A-202 (the entry's form stays; the build module derives the same-repository tree, 22:26)** Met in the review of
|
||||
H-A-198/199: writing "../" paths into the entry changes the form of the catalog seat's `modules` value, which every
|
||||
module decodes, so every reader (the builder, the build modules, the assigner, the runner) would have to run the new
|
||||
client before the indexer writes one; the mesh cannot derive that ordering edge yet (an H2 finding). So H-A-198 and
|
||||
H-A-199 are amended: the entry's `paths` keep the manifest's form; the Go build module derives, from the fetched
|
||||
tree's go.mod files, every same-repository module directory a fetched module requires at the zero version,
|
||||
transitively (it already does so one level deep), and keeps them in the narrowed tree; and the indexer takes those
|
||||
directories' objects into the fingerprint for every form (a line per derived directory and its object, appended to
|
||||
the tree input, as H-A-172 asks), without writing them into the entry. The pins of H-A-201 stand. P1, P7, P4.
|
||||
|
||||
Reference in New Issue
Block a user