mirror of
https://github.com/theupriser/steamify-cachyos-live-iso.git
synced 2026-10-02 15:10:26 +02:00
theupriser
ad246253c7
TODO.md should stay a plain task list; the Calamares module/build gotchas, QMP-driving quirks, ISO permission pitfall and build-VM SSH flakiness notes now live in AGENTS.md instead.
90 lines
5.1 KiB
Markdown
90 lines
5.1 KiB
Markdown
# To do (Steam Machine edition)
|
|
|
|
## Open
|
|
|
|
1. **Steamify installer page** (2026-09-28, working end to end; see
|
|
`AGENTS.md` for the module/build/testing details and gotchas behind
|
|
this). `packagechooserq` (custom QML) is built out of tree and baked
|
|
straight into `archiso/airootfs/usr/lib/calamares/modules/packagechooserq/`.
|
|
`netinstall` (checkbox tree) stays as a manually-swappable fallback
|
|
(`steamify-cachyos-dev/share/sn.sh` + `nisteamify.conf`) for when the
|
|
module can't load, but isn't wired into `calamares-online.sh`
|
|
automatically yet.
|
|
- **Still open**:
|
|
- Bake the `packagechooserq` *build* into the ISO build pipeline
|
|
itself (a `build-calamares-modules.sh` step: install
|
|
`cachyos-calamares-next`, build out of tree, install into
|
|
`airootfs`) instead of committing a prebuilt `.so`, so it always
|
|
matches whatever Calamares version is current at build time.
|
|
- Version-mismatch fallback: after `calamares-online.sh`'s
|
|
`pacman -Sy cachyos-calamares-next`, check the installed version
|
|
against what the module was built for; on a mismatch, switch
|
|
`settings.conf` to the `netinstall` page instead (generate its
|
|
groups conf from `--defaults --list` there too) rather than risk an
|
|
"Initialization Failed" module.
|
|
- "Boot into gaming mode" as an opt-out sub-toggle under SteamOS
|
|
conversion (agreed with the user) isn't implemented on either page
|
|
yet — both still use the old Gaming/Desktop radio-row.
|
|
- A Python job (e.g. `steamifychoice`, before `packages@online`) to
|
|
normalize either page's choice (packagechooserq's
|
|
`packagechooser_steamifypage` GS key, or netinstall's
|
|
packageOperations markers) into one `steamifyChoice` GS key, so
|
|
`shellprocess_steamify.conf` doesn't need to know which page ran.
|
|
|
|
2. **Check the live name** (the build tree has it right:
|
|
`build/x86_64/airootfs/etc/os-release`) after the next build: Hello's subtitle should say
|
|
"Steamify CachyOS, based on CachyOS rolling" (`steamify-customize.sh`,
|
|
run by mkarchiso after the packages; the airootfs copy of os-release is
|
|
overwritten by a package).
|
|
3. ~~Steamify PR for `feat/defaults-options`~~ — done: 2.7.0 (`--options`,
|
|
`--boot`, `steamify.sh --boot` standalone) and 2.8.0
|
|
(`--defaults --list`, what the Steamify page's rows come from) are both
|
|
released. **The ISO builder is up to date with this**: no checkout
|
|
argument needed, `steamify-prepare.sh` (no args) and `calamares-online.sh`
|
|
at boot both just fetch the newest release, so the ISO always has 2.8.0+
|
|
without a rebuild for a Steamify-side change alone. Only pass
|
|
`steamify-prepare.sh <checkout>` / `vmisobuild.sh --steamify <path>` when
|
|
testing an *unreleased* Steamify change.
|
|
4. **Build in the test VM** instead of on the Steam Machine
|
|
(steam-machine-iso skill), and install the result unattended with
|
|
`scripts/vminstall.sh --iso` (vm-install skill; the Calamares Steamify
|
|
step then needs `steamify-install` run from the live script).
|
|
5. **Test on the real Steam Machine** from a USB stick (gamescope, LEDs, CEC,
|
|
power-off) before calling the ISO usable.
|
|
|
|
## Done
|
|
|
|
- **Steamify 2.6.0** released (`--defaults`, install-time mode).
|
|
- **Live session** (VM, `--fremont`): Vapor look and layout (Steam Deck
|
|
wallpaper) at the live login; the power-off module is built for both ISO
|
|
kernels and loaded at boot, in the VM it returns "No such device" (no
|
|
AMDI0030 GPIO controller), as designed. Whether it keeps the real Steam
|
|
Machine off is part of the hardware test.
|
|
- **Regression test 2.6.0 on an existing desktop install** (test VM from
|
|
ssh-ready, `--fremont`): full first run, re-apply, notifications/CEC/theme
|
|
off and on again. No errors; user units enabled and running, theme applied
|
|
and restored live, no first-login autostart with a session.
|
|
- **ISO name**: `steamify-cachyos-<date>-x86_64.iso` (`iso_name` in
|
|
`archiso/profiledef.sh`); the volume label stays `COS_<yyyymm>`.
|
|
- **VM install from the ISO (2026-09-27, `f42859a`):** a VM install from the ISO (Hello's
|
|
Install, no manual fixes) ran Steamify's step: every component OK,
|
|
`exit: 0`, SDDM autologin into gamescope. First desktop login (session switched to plasma in the VM) passed too:
|
|
Vapor layout, the app opened with everything on. The first-login script
|
|
runs the newest *release*, so it only works once 2.6.0 is released (in the
|
|
test it was pointed at the bundle).
|
|
The VM's text
|
|
console doesn't show (virgl): read the installed disk with
|
|
`qemu-nbd -r` + `mount -o ro,rescue=nologreplay,subvol=@` (logs in `@log`).
|
|
|
|
## Later
|
|
|
|
- **Branding**: the live session's os-release says "Steamify, based on
|
|
CachyOS" (Hello's subtitle); Hello's window title and the boot menu still
|
|
say CachyOS. Check with the CachyOS team.
|
|
- **Release**: a CI job that builds the ISO (privileged container, flags from
|
|
the steam-machine-iso skill) and hosts it (>2 GB, not a GitHub release asset).
|
|
- **Drop the Boost 1.91 workaround** in `steamify-prepare.sh` once
|
|
`cachyos-calamares-next` is rebuilt against the repos' Boost.
|
|
|
|
Build and test details: the `steam-machine-iso` skill in steamify-cachyos-dev.
|