Explain pinned local ISO builds on the BOS site #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/bos-37-site-pinned-local-build"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Website portion of BOS-37. The Build from source section now explains that local ISO builds stage lockfile-pinned bread tools from a signed bakery index into a temporary home by default. It also documents
sudo BAKE_FROM_HOME=1 ./build-local.shfor development builds using installed bakery versions.This PR is stacked on bos-site PR #1, which imports the static source for bos.breadway.dev. The companion BOS implementation is Breadway/bos PR #59. Neither PR deploys the live page.
Verified the wording against the BOS PR #59 README and its clean Arch ISO acceptance record. Parsed index.html with Python's HTMLParser and ran
git diff --check. The static site has no build step or CI workflow.Review verdict
The BOS-37 site-copy criteria are met in this PR:
index.html:1446-1451now describes the signed, lockfile-pinned default and theBAKE_FROM_HOME=1development override. The wording matches the BOS PR #59 README and acceptance record. The one-line changelog entry is in scope.This is the correct
Breadway/bos-siterepository, with PR #4 based on PR #1, the source import for the actualbos.breadway.devsite. The branch is mergeable and has no CI status because the static site has no CI workflow. PR #1 has a review finding about internal deployment details; keep this PR open and stacked until that dependency is reworked.Pull request closed