Skip to content

Build Fedora/RHEL RPM package in release workflow - #27

Open
overcuriousity wants to merge 1 commit into
pawlaszczyk:masterfrom
overcuriousity:feat/fedora-rpm-package
Open

Build Fedora/RHEL RPM package in release workflow#27
overcuriousity wants to merge 1 commit into
pawlaszczyk:masterfrom
overcuriousity:feat/fedora-rpm-package

Conversation

@overcuriousity

Copy link
Copy Markdown

Summary

FQLite releases currently ship a .deb for Linux, but nothing installable on Fedora/RHEL-family systems. This PR adds an .rpm artifact to the release builds.

Changes

  • build.gradle: new optional Gradle property -PinstallerType that is forwarded to jpackage's --type on Linux (jpackage otherwise defaults to the native package type of the build host, i.e. deb on the Ubuntu runner). When building an RPM, the Apache-2.0 license tag (--linux-rpm-license-type 'ASL 2.0') is set as well.
  • .github/workflows/build.yml and build_secure.yml: after the existing deb step on the Ubuntu runner, install rpm (provides rpmbuild, which jpackage needs for --type rpm), rebuild with -PinstallerType=rpm, and attest + upload the resulting fqlite-<version>-x86_64.rpm alongside the other artifacts. The publish job picks it up automatically since it collects artifacts/*.

No change to the existing deb/dmg/exe outputs.

Testing

Local verification wasn't possible (host has only JDK 25; Gradle 8.10.2 doesn't run on it), so the workflow run on this branch is the intended verification — happy to iterate if the RPM step needs adjustment.

🤖 Generated with Claude Code

jpackage only produces the native package type of the build host, so the
Ubuntu CI job so far only shipped a .deb. Add an -PinstallerType Gradle
property that forwards to jpackage --type, and a second CI step on the
Ubuntu runner that installs rpmbuild and builds an RPM (with Apache-2.0
license tag). The RPM is attested and uploaded like the other artifacts,
so it lands in the GitHub release automatically.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant