Answer A-418: a bundle's or archive's name for reserved is <module>/<artifact> from its entry's artifact reference
This commit is contained in:
@@ -1045,3 +1045,10 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
holds none, it takes the bytes from the artifact store by that digest, as A-73 and A-50 say, and stores and tags them;
|
||||
when neither has it, it refuses as not stored, naming the digest. The builder's publish again names its transfer in
|
||||
the transfer form the build's own step uses.
|
||||
- **A-418** (§478, §676, §694, A-417; live, the control-node 2026-11-15 02:57: the tag of mesh-delivery-pipeline 0.1.6 is
|
||||
refused since the builder's `reserved` answers "no entry carries the name mesh-delivery-pipeline/program": it matches a
|
||||
name only against an artifact's `package`, which a bundle or an archive has none of, so no bundle is ever found;
|
||||
principles 7 and 8) A bundle's or an archive's name for `reserved` is `<module>/<artifact>`, read from its catalog
|
||||
entry's artifact reference (`<module>:<artifact>`), the name the build step and the builder publish it under; the
|
||||
entry stays the one source of the name, and no `package` is added to it. A name that matches no entry is said in the
|
||||
builder's log with the entries looked at.
|
||||
|
||||
Reference in New Issue
Block a user