Summary
Expand ProtonPlus GitHub releases with native Linux packages in addition to the existing AppImage, making ProtonPlus easier to install directly on more distributions and architectures.
Proposed Implementation
-
Automatically build release packages through GitHub Actions when a new ProtonPlus version is tagged.
-
Provide native packages for:
- Debian/Ubuntu (
.deb)
- Fedora/RPM-based distributions (
.rpm)
- Arch Linux (
.pkg.tar.zst)
-
Keep the existing AppImage release artifact.
-
Support both x86_64 and aarch64 where the application and required dependencies support them.
-
Keep the native packaging definitions in the ProtonPlus repository so they can be versioned and maintained alongside the application.
-
Generate packages from the same tagged ProtonPlus source to keep all release formats consistent.
-
Add automated CI checks that install generated packages in clean environments and verify:
- Package installation
- ProtonPlus executable
- Desktop/AppStream metadata
- Icons
- GSettings schemas
- Required runtime dependencies
-
Generate checksums for release artifacts.
-
Publish a versioned source archive alongside binary packages.
-
Allow distribution packaging such as the AUR package to consume the official ProtonPlus release sources/artifacts instead of maintaining separate upstream sources.
Goal
Provide consistent first-party ProtonPlus packages across major Linux distribution families, reduce reliance on third-party packaging, improve installation accessibility, and ensure release packages are automatically built and tested from the same official source.
Summary
Expand ProtonPlus GitHub releases with native Linux packages in addition to the existing AppImage, making ProtonPlus easier to install directly on more distributions and architectures.
Proposed Implementation
Automatically build release packages through GitHub Actions when a new ProtonPlus version is tagged.
Provide native packages for:
.deb).rpm).pkg.tar.zst)Keep the existing AppImage release artifact.
Support both
x86_64andaarch64where the application and required dependencies support them.Keep the native packaging definitions in the ProtonPlus repository so they can be versioned and maintained alongside the application.
Generate packages from the same tagged ProtonPlus source to keep all release formats consistent.
Add automated CI checks that install generated packages in clean environments and verify:
Generate checksums for release artifacts.
Publish a versioned source archive alongside binary packages.
Allow distribution packaging such as the AUR package to consume the official ProtonPlus release sources/artifacts instead of maintaining separate upstream sources.
Goal
Provide consistent first-party ProtonPlus packages across major Linux distribution families, reduce reliance on third-party packaging, improve installation accessibility, and ensure release packages are automatically built and tested from the same official source.