Skip to content

Flatpak: runtime refresh, tag CI bundle, README, Boost without tests - #118

Merged
vigri merged 3 commits into
ScanTailor-Advanced:masterfrom
pablogventura:feature/flatpak-manifest-ci-docs
Apr 20, 2026
Merged

Flatpak: runtime refresh, tag CI bundle, README, Boost without tests#118
vigri merged 3 commits into
ScanTailor-Advanced:masterfrom
pablogventura:feature/flatpak-manifest-ci-docs

Conversation

@pablogventura

Copy link
Copy Markdown

Summary

  • Manifest (flatpak/org.scantailor.Advanced.json): bump KDE org.kde.Platform / org.kde.Sdk to 5.15-24.08 (supported on Flathub); remove redundant base / base-version entries. Source tag remains v1.1.1 (current upstream release).
  • CMake: Boost::unit_test_framework is only required when BUILD_TESTS=ON; with -DBUILD_TESTS=OFF (Flatpak) only header libraries are required. Helps chroot/Flatpak builds (see issue imageproc_tests fails when building offline in clean chroot #61).
  • CI: new .github/workflows/flatpak.yml — runs on v* tag pushes and workflow_dispatch, uploads a .flatpak artifact for smoke testing (not a Flathub publish pipeline).
  • README: table clarifying GitHub Releases vs Flathub submission vs local flatpak-builder, with links to Flathub author docs and #105.

Relation to Flathub / #105

This PR does not complete Flathub distribution by itself; it makes the in-repo manifest and build path more credible for a future Flathub submission and gives maintainers an automated bundle on tags.

Relates to #105 (does not close Flathub listing).

- flatpak: KDE Platform/Sdk 5.15-24.08, drop redundant base/base-version
- CMake: require Boost unit_test_framework only when BUILD_TESTS=ON
- GHA: flatpak workflow on v* tags and workflow_dispatch with .flatpak artifact
- README: clarify Releases vs Flathub vs local build and submission docs
@vigri
vigri merged commit 2b8372d into ScanTailor-Advanced:master Apr 20, 2026
3 checks passed
@pablogventura
pablogventura deleted the feature/flatpak-manifest-ci-docs branch May 24, 2026 02:23
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.

2 participants