From 3e5476336765bff3c13d9b0d9c9adafb2d2fd32a Mon Sep 17 00:00:00 2001 From: Michael Chus Date: Sat, 28 Mar 2026 21:38:54 +0300 Subject: [PATCH] docs: add iso-build-rules (verify package names before use) Co-Authored-By: Claude Sonnet 4.6 --- bible-local/docs/iso-build-rules.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 bible-local/docs/iso-build-rules.md diff --git a/bible-local/docs/iso-build-rules.md b/bible-local/docs/iso-build-rules.md new file mode 100644 index 0000000..61d4d5e --- /dev/null +++ b/bible-local/docs/iso-build-rules.md @@ -0,0 +1,21 @@ +# ISO Build Rules + +## Verify package names before use + +ISO builds take 30–60 minutes. A wrong package name wastes an entire build cycle. + +**Rule: before adding any Debian package name to the ISO config, verify it exists and check its file list.** + +Use one of: +- `https://packages.debian.org/bookworm/` — existence + description +- `https://packages.debian.org/bookworm/amd64//filelist` — exact files installed +- `apt-cache show ` inside a Debian bookworm container + +This applies to: +- `iso/builder/config/package-lists/*.list.chroot` +- Any package referenced in `grub.cfg`, hooks, or overlay scripts (e.g. file paths like `/boot/memtest86+x64.bin`) + +## Example of what goes wrong without this + +`memtest86+` in Debian bookworm installs `/boot/memtest86+x64.bin`, not `/boot/memtest86+.bin`. +Guessing the filename caused a broken GRUB entry that only surfaced at boot time, after a full rebuild.