From afe9d5cdb2a827eb9917d9ff8c1407c53d5f97a7 Mon Sep 17 00:00:00 2001 From: Josh Knapp Date: Thu, 17 Sep 2026 10:01:29 -0700 Subject: [PATCH] docs: correct Linux packaging in BUILDING.md BUILDING.md listed AppImage, .deb and .rpm as build artifacts, but Linux ships as AppImage only -- CI passes `--bundles appimage`, and the .deb and .rpm were dropped because neither could self-update. A bare `npx tauri build` still emits all three, since tauri.conf.json keeps "targets": "all" to leave macOS and Windows untouched, so the table now marks which are actually released rather than pretending the others do not exist. Co-Authored-By: Claude Opus 5 (1M context) --- BUILDING.md | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/BUILDING.md b/BUILDING.md index 2d3580a..d43c786 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -71,13 +71,29 @@ npm ci npx tauri build ``` +Linux ships as **AppImage only**. To match what CI produces, pass the bundle +explicitly: + +```bash +npx tauri build --bundles appimage +``` + +The `.deb` and `.rpm` bundles were dropped — two more artifacts to build and +publish for an audience the AppImage already serves, and neither could +self-update. A bare `npx tauri build` still emits them, because +`tauri.conf.json` keeps `"targets": "all"` so that macOS and Windows are +untouched; they are not released and not tested. + Build artifacts are located in `app/src-tauri/target/release/bundle/`: -| Format | Path | -|------------|-------------------------------| -| AppImage | `appimage/*.AppImage` | -| Debian pkg | `deb/*.deb` | -| RPM pkg | `rpm/*.rpm` | +| Format | Path | Released | +|------------|-------------------------------|----------| +| AppImage | `appimage/*.AppImage` | yes | +| Debian pkg | `deb/*.deb` | no | +| RPM pkg | `rpm/*.rpm` | no | + +`scripts/finalize-appimage.sh` post-processes the AppImage; see the Packaging +section of `CLAUDE.md` for why both of its steps are load-bearing. ## macOS