Migrate live ISO to Titanoboa's contract model: Glarion branding + install-from-live #4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Rebuild the live ISO pipeline on Titanoboa's current "container-native ISO contract" architecture. Unlocks: GRUB menu/ISO label saying "Glarion" (currently "Fedora Linux 44 Live ISO"), an install path inside the live session, and a maintained upstream (we currently pin the abandoned v0.2 with just 1.51.0 as a workaround).
Plan document (source of truth): Obsidian vault,
Personal/Projects/glarion/plans/2026-07-13-titanoboa-contract-migration.md.Checklist:
iso/payload-image directory: Containerfile,src/build.sh(adapted from titanoboa's bazzite example, reusingconfig/flatpaks.list),src/iso.yamlwith Glarion-Live label and branded GRUB entriesbuild-live-iso.yml: build payload image, run Titanoboa pinned to a main-branch SHA, keep checksum + guarded R2 uploadtest-live-iso.yml: add ~8s screenshot to capture the GRUB menu; verify branding, desktop, flatpaks, install pathRelated: #2 (current v0.2-based live ISO, stays published until this lands), #3 (first-boot flatpaks gap — the installed-system side of the same app-set story).
Scope update from the clean-install product decision (see #3): the live ISO's flatpaks are explicitly demo content only — nothing about them carries to installed systems.
config/flatpaks.listis trimmed to Chrome + Steam (commitdbd6edd), which should also shrink the rebuilt live ISO meaningfully from 9.8 GiB. When sizing the install-payload embedding decision, use the smaller demo-set baseline.