Carry varve-serve: the layer shipped documentation and not its viewer - #18
Merged
Merged
Conversation
This realm has carried a `docs` payload since v0.35.0 — `varve-core-api`, the rustdoc for the crate it also carries — and has never carried the one tool that reads it. `varve-serve` exists for exactly this: it reads documentation payloads out of the STORE, against the signed manifest, with no export step. A consumer of this layer therefore had the documentation and no way to open it short of exporting the tree by hand — which is the workaround `export-docs` exists to make unnecessary. It is published for all four triples and has been since v0.35.0. Checked against the v0.38.0 release rather than assumed, and `varve-producer plan` resolves every one: varve-serve aarch64-apple-darwin varve-serve-v0.38.0-aarch64-apple-darwin.tar.gz varve-serve x86_64-apple-darwin varve-serve-v0.38.0-x86_64-apple-darwin.tar.gz varve-serve aarch64-unknown-linux-gnu varve-serve-v0.38.0-aarch64-unknown-linux-gnu.tar.gz varve-serve x86_64-unknown-linux-gnu varve-serve-v0.38.0-x86_64-unknown-linux-gnu.tar.gz Same shape as the assembler beside it: `repo` is spelled out because the payload's name is not the repository's, and the default asset template already names the archives exactly, so no `asset` is needed. `varve` itself stays out, deliberately. It is what INSTALLS this layer, so a consumer already has it before the layer exists for them; carrying it would put the bootstrap inside the thing it bootstraps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019TNtfRjLNhEz82G2ggeeNu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This realm has carried a
docspayload since v0.35.0 —varve-core-api, therustdoc for the crate it also carries — and has never carried the tool that
reads it.
varve-serveexists for exactly that: it reads documentation payloads out ofthe store, against the signed manifest, with no export step. A consumer of
this layer had the documentation and no way to open it short of exporting the
tree by hand.
Checked, not assumed
varve-servehas been published for all four triples since v0.35.0.varve-producer planagainst this manifest resolves every one:Same shape as the assembler beside it:
repospelled out because thepayload's name is not the repository's, and the default asset template already
names the archives exactly.
What stays out, and why
varveitself. It is what installs this layer, so a consumer has itbefore the layer exists for them; carrying it would put the bootstrap inside
the thing it bootstraps.