mirror of
https://github.com/AZumD/frametop.git
synced 2026-10-27 14:00:26 +01:00
DeeJanuzandClaude Opus 5.5
eae2f0b754
get.sh --release reads a release list (frametop.release/v1: releases/stable.json or experimental.json on Frametop's page, or --manifest), picks the newest release tested on this SteamOS build, else the newest not known to break on it (asking first), and refuses a build every release breaks on (--any-steamos overrides). It pulls the release's image by digest, copies the image's /src/frametop out to ~/.local/share/frametop/releases/VERSION with a .frametop-release (version, image, commit, channel, container), and runs that copy's install.sh. The release before stays, for going back; older ones go, with their containers and images. In a release tree (FRAME_RELEASE in _env.sh), install.sh builds nothing: it installs the distrobox the image brings (pack/build/distrobox) and makes the release's own container from its image (pack/release-box.sh, named after the digest, so installing a release never stops the one running). scripts/in-box then runs the programs there. install.sh also gets --bluetooth, to install the Bluetooth fixes without asking. pack/steamos.json is the SteamOS table: builds tested, and builds that break releases from "from" up to "fixed_in". pack/release-manifest.py writes release lists with it, for CI. The pick logic and the lists are tested offline (pack/test/release-test.py, in the gate). uninstall.sh removes releases, their containers, and their images in its second step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>