Linux release checks¶
Use this after building a Linux bundle. Build checks alone do not establish desktop or GPU acceptance.
Validate¶
python3 packaging/linux/build_container.py --libc glibc --check
python3 packaging/linux/build_container.py --libc musl --check
| Check | Recorded status |
|---|---|
| ARM64 images, 17 packaging tests and relocation fixture | Passed on Ubuntu 22.04 and Alpine 3.22 |
| ARM64 CLI/server, extension and AccessKit compilation | Passed in both images |
| Seven headless terminal-scene tests | Passed against both CLIs |
| ABI checks | glibc CLI ≤2.35; musl CLI has no glibc requirement |
| Complete exports and desktop acceptance | Unverified |
| x86_64 | Not yet exercised |
Earlier Colima relocation and cached-binary checks validate the layout approach, not current-source releases. Container checks do not establish GPU-driver or minimum-kernel support.
Publish¶
- Test the extracted bundle on a clean target desktop.
- Verify launch, terminal input/IME, dock grouping and optional Chromium.
- Include licences and required redistribution notices.
- Upload archives with a top-level
SHA256SUMScovering every release asset. - Follow the Linux installation guide to test the public installer.
Do not overwrite checksum entries for Windows or macOS when adding Linux assets.
Install layout¶
- Versions live under
~/.local/share/graffitty/installs/. - The
currentsymlink changes only after verification, so running apps keep their current files. - Commands live in
~/.local/bin/. - User data stays outside version directories.
- The installer registers desktop and file-manager entries without root access.