readme: document AppImage channel + libfuse2 requirement
The Pre-built releases section had no AppImage entry. Add one with the per-distro libfuse2 package names and an APPIMAGE_EXTRACT_AND_RUN escape hatch for hosts that no longer ship FUSE 2 by default. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
21
README.md
21
README.md
@@ -27,6 +27,27 @@ Pre-built artifacts are published at
|
||||
runnable directly, no Python installation required on the host. Lua
|
||||
support still needs a system `lua` interpreter and the `lua-socket` /
|
||||
`lua-cjson` modules.
|
||||
* **AppImage** (`Testium-<version>-x86_64.AppImage`) — single-file
|
||||
Linux binary, runnable directly:
|
||||
|
||||
```sh
|
||||
chmod +x Testium-*-x86_64.AppImage
|
||||
./Testium-*-x86_64.AppImage
|
||||
```
|
||||
|
||||
Requires `libfuse2` on the host (FUSE 2 — distinct from `fuse3`, which
|
||||
most distros now ship by default):
|
||||
|
||||
| Distro | Package |
|
||||
|--------|---------|
|
||||
| Arch / CachyOS / Manjaro | `fuse2` |
|
||||
| Debian trixie / Ubuntu 24.04+ | `libfuse2t64` |
|
||||
| Debian bookworm / Ubuntu 22.04 | `libfuse2` |
|
||||
| Fedora | `fuse-libs` |
|
||||
|
||||
If you can't install libfuse2 (e.g. minimal container), prefix the
|
||||
invocation with `APPIMAGE_EXTRACT_AND_RUN=1` — the AppImage will
|
||||
self-extract to `/tmp` on each run instead of FUSE-mounting.
|
||||
* **Flatpak bundle** (`testium.flatpak`) — install with:
|
||||
|
||||
```sh
|
||||
|
||||
Reference in New Issue
Block a user