Currently, PictoPy provides Linux distribution via a DEB package, which works well for Debian-based systems (Ubuntu, Debian, Mint, etc.). However, users on RPM-based distributions such as Fedora, RHEL, Rocky Linux, AlmaLinux, and openSUSE cannot install PictoPy using their native package manager.
This limits adoption on a significant portion of the Linux ecosystem and requires users to rely on manual binaries or unsupported installation methods.
Proposed Solution
Add RPM package support using Tauri’s built-in RPM bundler.
This would involve:
Enabling the rpm target in tauri.conf.json
Defining RPM-specific dependencies (similar to the existing DEB configuration)
Ensuring bundled resources and sidecars are included correctly
Verifying installation on Fedora-based systems
Tauri already supports RPM packaging, so this should integrate cleanly with the existing build pipeline.
Why This Is Useful
Expands PictoPy’s Linux support beyond Debian-based distros
Improves user experience by allowing native installation via dnf
Aligns with best practices for cross-distro Linux distribution
Makes PictoPy more accessible to contributors and users on Fedora/RHEL systems
Acceptance Criteria
A .rpm package is generated during tauri build on Linux
The package installs cleanly on Fedora-based systems
Application launches successfully after installation
No regression to existing DEB, Windows (NSIS), or macOS builds
Additional Notes
This change is complementary to the existing DEB setup and does not replace it.
Future improvements could include CI automation to build and publish RPM artifacts.
Currently, PictoPy provides Linux distribution via a DEB package, which works well for Debian-based systems (Ubuntu, Debian, Mint, etc.). However, users on RPM-based distributions such as Fedora, RHEL, Rocky Linux, AlmaLinux, and openSUSE cannot install PictoPy using their native package manager.
This limits adoption on a significant portion of the Linux ecosystem and requires users to rely on manual binaries or unsupported installation methods.
Proposed Solution
Add RPM package support using Tauri’s built-in RPM bundler.
This would involve:
Enabling the rpm target in tauri.conf.json
Defining RPM-specific dependencies (similar to the existing DEB configuration)
Ensuring bundled resources and sidecars are included correctly
Verifying installation on Fedora-based systems
Tauri already supports RPM packaging, so this should integrate cleanly with the existing build pipeline.
Why This Is Useful
Expands PictoPy’s Linux support beyond Debian-based distros
Improves user experience by allowing native installation via dnf
Aligns with best practices for cross-distro Linux distribution
Makes PictoPy more accessible to contributors and users on Fedora/RHEL systems
Acceptance Criteria
A .rpm package is generated during tauri build on Linux
The package installs cleanly on Fedora-based systems
Application launches successfully after installation
No regression to existing DEB, Windows (NSIS), or macOS builds
Additional Notes
This change is complementary to the existing DEB setup and does not replace it.
Future improvements could include CI automation to build and publish RPM artifacts.