tauri-linux-packaging_skill

Overview

This skill guides you through packaging Tauri v2 desktop apps for Linux distributions, covering AppImage, Debian (.deb), RPM, Flatpak, Snap, and AUR. It focuses on practical build settings, cross-compilation tips, signing, and publishing steps so you can produce reproducible installable artifacts. Expect concrete commands, manifest examples, and CI recommendations for reliable releases.

How this skill works

The skill inspects common packaging targets and provides configuration examples for Tauri bundling options, platform-specific manifests (flatpak, snapcraft, PKGBUILD), and package metadata (deb, rpm). It explains build-time requirements like glibc compatibility and toolchains, cross-compilation steps (ARM/aarch64), signing procedures, and CI integration using Docker or GitHub Actions. It also covers runtime fixes (PATH), tray icon adjustments for Flatpak, and debug commands for RPM and other bundles.

When to use it

• Preparing a single-file portable AppImage for wide distribution
• Creating native .deb or .rpm packages for repos or apt/dnf installs
• Publishing to sandboxed platforms like Flatpak/Flathub
• Packaging and uploading a Snap to the Snap Store
• Creating an AUR package or PKGBUILD for Arch users

Best practices

• Build on the oldest glibc base you intend to support (use Docker/GitHub Actions for reproducible builds).
• Include only required system deps in package metadata and prefer runtime deps like libwebkit2gtk-4.1-0.
• Use platform-specific signing (GPG for RPM, Snap/Flathub/Snapcraft flows) and protect private keys in CI secrets.
• Test packages locally with provided debug commands (rpm -qip, flatpak run, snap run, makepkg -si).
• Provide desktop file, icons, and metainfo to ensure correct integration with menus/tray and app stores.

Example use cases

• Build AppImage for portable distribution to testers and users who don’t want installation.
• Produce .deb and .rpm bundles for Debian/Ubuntu and Fedora/RHEL repositories with correct Depends and post-install scripts.
• Create a Flatpak manifest and metainfo to submit the app to Flathub with sandbox permissions configured.
• Use Snapcraft to build and publish a strict-confinement Snap to the Snap Store including necessary lib bindings.
• Prepare PKGBUILD (binary or source) and myapp.install to submit to AUR so Arch users can install via pacman helpers.