feat(build): COMPRESS_IMG=1 emits .img.xz + .sha256 — the pair the skill and runbook already promise #279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/compress-img-flag"
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?
Grew out of the blank-spaces sweep, via the other agent's find:
skills/iso-build/SKILL.mdlists.img.xz+.img.xz.sha256as typical artifacts andRELEASE-BUILD-RUNBOOK.md's publish checklist requires the pair — but nothing in the pipeline ever produced them.Changes (opt-in, default off):
build.cfg:COMPRESS_IMG="${COMPRESS_IMG:-0}"knob next to the other build knobs.build.sh: after the step-6 report,xz -T0 -f -kthe output image and writesha256 > .img.xz.sha256.-kkeeps the raw.imgsoddneeds no decompress round-trip. Sparse holes are zeros and compress at memory speed; the time cost is the ~8G of real data..xzgoes anywhere. (Today'sclawdie-quindecim-0.13.0.imgis exactly that case: keys baked, LAN-only, must NOT hit the iso-publish lane.)Deliberately NOT added to the doas nopass keep-list — set via build.cfg or
doas env(catch-all rule).Gates:
sh -n build.shclean,./scripts/check-format.shgreen.🤖 Generated with Claude Code