What problem does it solve? Distributing Tauri v2 desktop applications on Linux requires navigating six different packaging formats, each with its own configuration, dependency declarations, signing requirements, and store submission rules, which is error-prone without a consolidated reference. ## Core Features & Use Cases - Multi-Format Bundle Configuration: Provides complete tauri.conf.json settings and build commands for AppImage, Debian (.deb), and RPM packages, including dependency lists, install scripts, and GPG signing. - Sandboxed Store Packaging: Supplies working Flatpak manifests with MetaInfo files and Flathub submission steps, plus snapcraft.yaml configurations with confinement plugs and layout bindings. - Arch and ARM Support: Covers AUR PKGBUILD templates for binary and source builds, plus ARM64 cross-compilation setup with linker configuration. - Use Case: You have finished a Tauri v2 app and need to publish it to Flathub, the Snap Store, and the AUR while also producing AppImage and deb artifacts in a GitHub Actions release pipeline. ## Quick Start Ask the assistant to package your Tauri v2 app as a Flatpak and generate the manifest, MetaInfo file, and build commands for Flathub submission.
