Skip to content

Packaging

Format Command Output
.deb, .rpm, .AppImage ./scripts/build-packages.sh target/release/bundle/{deb,rpm,appimage}/
AUR (penates-bin) installs the release tarball’s binaries; files in packaging/aur/penates-bin see RELEASING
Arch package (penates-bin, for pacman -U) scripts/make-arch-package.sh on Arch (not as root): the AUR penates-bin PKGBUILD pointed at the local tarball; the Release workflow runs it in an archlinux:base-devel container dist/penates-bin-<ver>-1-x86_64.pkg.tar.zst, attached to the release
AUR (penates) builds the tagged source with cargo (x86_64 and aarch64); files in packaging/aur/penates both refreshed by scripts/publish-release.py
Arch / CachyOS (local) cd packaging/arch && makepkg -si penates-<ver>-1-x86_64.pkg.tar.zst
Portable tarball (any *nix) ./scripts/make-tarball.sh dist/penates-<ver>-<triple>.tar.gz (contains install.sh; PREFIX=$HOME/.local ./install.sh)
Windows (NSIS), macOS (.app, .dmg) push a v* tag; .github/workflows/release.yml a draft GitHub release

Build tools: cargo install tauri-cli --version "^2" --locked. The first AppImage build downloads linuxdeploy. Signed builds need the updater key (~/.tauri/penates.key, or TAURI_SIGNING_PRIVATE_KEY); see RELEASING.

  • penates (CLI) and penates-desktop must sit side by side; the CLI finds the GUI next to itself. The Tauri bundle ships the CLI as a sidecar (bundle.externalBin), and both .deb and .rpm install both binaries into /usr/bin.
  • Packaging-only settings live in src-tauri/tauri.bundle.conf.json (full icon list, sidecar, targets) so plain cargo build needs no prepared files. scripts/build-packages.sh stages the CLI as src-tauri/binaries/penates-<target-triple> and passes --config to cargo tauri build.
  • src-tauri/tauri.linux.conf.json (merged automatically on Linux) sets productName: penates and a desktop template so the launcher is penates.desktop with StartupWMClass=penates, matching the manager window’s app ID.
  • Inside an AppImage the running binary is in a temporary mount, so launchers use the $APPIMAGE path. The CLI is inside the AppImage but not on your PATH; use the .deb, .rpm, AUR package or tarball for the command line.
  • NO_STRIP=true is exported for AppImage builds because linuxdeploy trips on newer binutils.
  • Plain cargo build --release (tarball, PKGBUILD) needs --features penates-desktop/custom-protocol so the manager’s page is embedded.
  • The release profile optimizes for size (opt-level = "s"): about 10 MB for penates-desktop and 4 MB for penates.

THIRD-PARTY-LICENSES.txt (every Rust component’s copyright notices and license text, generated with scripts/gen-credits.py) ships in every package: /usr/share/doc/penates/ in the .deb, .rpm and AppImage, /usr/share/licenses/<package>/ from the AUR packages, beside LICENSE in the tarball, and inside the program (About → Credits → Full license texts). The AppImage also bundles system libraries (GTK, WebKitGTK, GLib and what they load), so scripts/build-packages.sh runs scripts/system-notices.sh to add SYSTEM-LIBRARIES.txt: each bundled library’s package, exact version, source package and license file.

Installs both binaries, the manager’s launcher (pointing at $PREFIX/bin/penates-desktop by full path, so it works when that folder is not on the desktop session’s PATH) and the icons, then refreshes the desktop’s caches. If the icon theme folder is not writable (it is sometimes left owned by root), the launcher points at a copy of the icon in $PREFIX/share/penates/ instead.

.deb and .rpm contents (both binaries, launcher, icons); the AppImage starts; the tarball installs into a scratch prefix and into ~/.local, and its launcher passes desktop-file-validate; makepkg builds the Arch package.

Windows and macOS installers by hand (CI builds, tests and smoke-tests the apps on every push; the Release workflow builds and signs them), installing the .deb/.rpm on their target distros, Apple notarization and Windows code signing (the installers are not signed with a platform certificate; see the README).