Add sqgipkg release packaging#96
Open
supercamel wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds optional sqgipkg packaging for Reminduck, similar to the Jorts packaging PR.
The goal is to provide a repeatable CI release path for:
This adds a sqgipkg.json manifest and GitHub Actions workflow. The workflow only runs on version tag pushes or manual dispatch, so normal development pushes are not affected.
Notes
The only project-side changes are small Meson/build tweaks needed for packaging and CI, and some autostart is disabled on Windows.
The packaging workflow uses Ubuntu 24.04/Noble as the reference CI environment, which provides Granite 7.4. Because of that, the packaging setup targets Granite 7.4 rather than Granite 7.7. Reminduck built cleanly with this setup and did not require code changes for Granite compatibility.
For the Windows build, autostart support is disabled because the current implementation depends on libportal, which is not available in the Windows packaging environment.
Testing
I tested the generated Windows .exe installer and confirmed that the installed app starts successfully.
I also checked that the application icons are bundled and display correctly.
Happy to adjust the packaging setup if you’d prefer it handled differently.