Repository navigation
Portability
Mel edited this page Nov 10, 2026
·
1 revision
Linux-agnostic audit of the whole tree (code, scripts, workflows, docs), Nov 2026. What was checked, what is supported, and the known limits.
Supported build/run distros, all x86_64:
| Distro | Versions | Notes |
|---|---|---|
| Debian | 12+ |
webkit2gtk-4.1 first shipped in bookworm |
| Ubuntu | 22.04+ | release baseline; libwebkit2gtk-4.1-dev verified on jammy |
| Fedora | 36+ | first with webkit2gtk4.1 split packages |
| Arch | current |
webkit2gtk-4.1 from extra |
Older distros that only ship webkit2gtk-4.0 (e.g. Ubuntu 20.04, Debian 11) cannot build or run this app: Tauri 2.12 / wry links against the 4.1 API. No other distro-specific code exists — the app reads $HOME / $XDG_CONFIG_HOME / $ESCACS_STACK and shells out to node and git found on PATH.
-
Hardcoded machine paths. Grepped code and scripts for
/home/, user names and user-specific cache paths. Clean: the only/home/...strings are the obviously fake/home/dev/...fixtures indev/mock-bridge.jsanddev/mock-app-bridge.js. Rust resolves the stack checkout from settings →$ESCACS_STACK→ upward walk (no home assumptions); scan roots use$HOMEwith aUSERPROFILEfallback. Scripts honour$HOMEand$XDG_CONFIG_HOME(with--dir/--config-home/--prefixoverrides). -
Distro package matrix. Every package name on Install was verified, not copied from memory: Arch names against the local pacman db, Ubuntu names against packages.ubuntu.com (jammy), Fedora names against Bodhi, and the full build lines against the Tauri v2 prerequisites. Two corrections came out of it: Arch needs
xdotool(shipslibxdo) andlibayatana-appindicator(libappindicator-gtk3no longer exists in Arch repos), and AppImage users need the WebKitGTK 4.1 runtime libs, which the bundle does not include. -
glibc baseline.
.github/workflows/release.ymlbuilds on ubuntu-22.04 (glibc 2.35) and carries a comment forbidding a casual runner bump — that glibc is the minimum the release AppImage/deb/rpm will run on.check.ymlandflatpak.ymluseubuntu-latest, which is fine: neither produces redistributed native bundles (check only runs tests; Flatpak pins the GNOME 51 runtime). -
Flatpak manifest sanity.
command: stack-appmatches the Cargo package/binary name; app-id matches the Tauri identifier.finish-argscover WebKit, updater/stack network fetches, and--filesystem=home. The file-chooser portal handles outside-home folders.sdk-extensionsstay unpinned; CI resolves them withflatpak-builder --install-deps-from=flathub --user. The runtimenodemodule uses the extension'sinstall.sh(node binary only). A minimal metainfo XML is installed to/app/share/metainfo. Config is deliberately NOT shared with the host: the sandbox remapsXDG_CONFIG_HOME, so the first sandboxed run re-picks the stack folder (or takes it from aflatpak override --env=ESCACS_STACK=...). Still draft: the generated npm/cargo vendor sources are uncommitted and no Flatpak build has run. -
Updater config sanity. Endpoint
.../releases/latest/download/latest.json,plugins.updater.active, andbundle.createUpdaterArtifactsare set intauri.conf.json; the baked-in pubkey byte-matches the generated key. Rust inits the updater + process plugins, capabilities allowupdater:default+process:allow-restart, startup does one silent non-blocking check, and the installed view offers check/download+install/relaunch. No update URL is hardcoded in the frontend — everything flows through the Tauri config.release.ymlhascontents: write, builds linux-only on the old runner viatauri-action@v0, and consumes theTAURI_SIGNING_PRIVATE_KEYsecret (empty password, so no password secret needed). Still untested end to end: cutting the firstv*release is a manual step — see Updates and Releases. -
Script robustness.
provision-stack.sh's no-JSON-tooling fallback now escapes its path before writingconfig.json.
- The Flatpak has never been built (missing vendor sources, no
flatpak-builderrun). The manifest is reviewed but unproven. - No real update has been installed yet:
v0.1.1is published with signed bundles andlatest.json, and the 404 that blocked checks is gone (repo is public), but no older install has checked, downloaded and relaunched yet. Needs: install the 0.1.1 AppImage, tagv0.1.2, then check-for-updates from the installed view and confirm the relaunch. - The window is frameless (
decorations: false) with a custom titlebar. Edge-resize on a frameless X11 window is compositor-dependent and was never verified headless — confirm drag/resize on target setups. - A locally built AppImage inherits its host glibc — only the CI (ubuntu-22.04) bundles are redistributable to older distros.
-
provision-stack.sh'sghpath was never exercised live (no auth in test sandboxes by design); the ssh and manual paths were. - The app never adds
~/escacs/stackto its own auto-lookup (settings → env → upward walk only). A host-side clone is found after provisioning because the script pins it intoconfig.json; if that file is wiped the app asks again instead of re-finding the clone. Candidates: teachresolve_stack_dir_innerthe default dir, or leave the explicit picker as the backstop.
See also: Install, Updates and Releases, Development.
Stack desktop client + CLI wiki — condensed from the repo docs. App repo: https://github.com/escacs/stack-app. CLI repo (private): https://github.com/escacs/stack.