Design 47 H: H-A-199, a step's paths may leave the module's directory, never the repository
This commit is contained in:
@@ -1062,3 +1062,9 @@ Where two preparers disagreed, the chosen one is named.
|
||||
same-repository module directory its go.mod requires, transitively, as the indexer derives them from the go.mod edges
|
||||
(H-A-157); a same-repository requirement is built from the tree, never pinned; a requirement of another repository
|
||||
is pinned by H-A-183. P7, P4 (the indexer owns the entry; the build modules only narrow by what it names).
|
||||
- **H-A-199 (a step's paths may leave the module's directory, never the repository, 22:12)** Met in the build of H-A-198:
|
||||
the step's paths are relative to the module's directory, so a same-repository sibling is "../<module>/<dir>", which
|
||||
the SDK's narrowing refuses as leaving the module and the Go build module passes straight to it. A path that leaves
|
||||
the module's directory but stays inside the repository is accepted and narrowed from the repository's root; one that
|
||||
leaves the repository is refused. The derived paths are part of the artifact's tree, so the fingerprint takes them in
|
||||
as it takes the manifest's named paths (H-A-172: what a build reads moves its fingerprint). P7, P1.
|
||||
|
||||
Reference in New Issue
Block a user