KomhandClaude Sonnet 5
94bb4f5ec9
OpenShot ships its Linux build only as an AppImage — no .deb, .rpm or plain tarball — which FlatPark's playbook has so far treated as a hard stop. It is not one: a type-2 AppImage is an ELF stub with a SquashFS image appended, and that image unpacks directly without the AppImage ever being executed or FUSE-mounted. This is the first app to use that route. Packaging: - extra-data, org.freedesktop.Platform//25.08. The AppImage is fully self-contained (its own Python 3.8, PyQt5, libopenshot, FFmpeg, Blender), so no KDE/GNOME runtime is needed — verified nothing in the bundle resolves against the runtime's Qt/Python, and the bundle ships no libGL/EGL/fontconfig to shadow it. - Second extra-data source: flatpark/prebuilt's appimage-tools-v1 (appimage-offset + unsquashfs, 54 KB). apply_extra computes the SquashFS offset from the ELF header and unpacks with unsquashfs -o; the AppImage and the extractor are deleted afterwards. Passes check-apply-extra.sh (root, all caps dropped, offline, /usr + /app/extra only). - Wrapper execs the AppDir's own usr/bin/openshot-qt-launch and pins QT_QPA_PLATFORM=xcb: the bundle ships the Qt5 wayland plugins but not the libQt5WaylandClient.so.5 they link, so wayland cannot initialise and Qt does not fall back on its own. Runs through XWayland. Sandbox: ipc, x11, dri, pulseaudio, network (update check / title templates / AI model download), xdg-videos/pictures/music/download for project footage, and --persist=.openshot_qt so OpenShot's state dir lands in the per-app directory rather than tmpfs or the real home. No --filesystem=home. dangerous_permissions is empty. OpenShot is on Flathub (currently 3.5.1, behind upstream's 4.0.0); this entry is primarily the AppImage-extraction mechanism proven end to end. Claude-Session: https://claude.ai/code/session_016F22CmZ197QR9hW3qiVxQC Co-authored-by: Claude Sonnet 5 <[email protected]>
Yet another Flatpak hub
FlatPark is a Flatpak hub for apps that ship as a definitive download, built to be driven by AI agents.
Goals
- AI-driven by design. Onboarding, review, publishing, upgrading, and cleanup are all meant to be driven by AI agents. Leaning on agents to do this work efficiently is a primary goal, not an afterthought.
- One runtime version, always the latest. Every app targets the current major of its runtime — never one app on GNOME 49 and another on 50. Old majors are dead weight on your disk, so the whole catalog moves forward together.
- extra-data only, no build hosting. FlatPark hosts only extra-data apps: it downloads official releases and repackages them — it never builds the app from source. (Supporting libraries the runtime lacks may be built from pinned source; the app itself is always the vendor's own binary.) That keeps installing and updating the apps you need in one place, while Flatpak keeps them sandboxed and out of your home directory.
- Open to vibe-coded apps, with guardrails. Apps built with AI ("vibe coding") are welcome, under clear rules enforced by AI review that weighs development history and app quality — and with an explicit de-listing process.
Install
flatpak --user remote-add --if-not-exists flatpark https://dl.flatpark.org/flatpark.flatpakrepo
flatpak --user install flatpark <app-id>
--user installs into your home (no admin); drop it from both commands for a
system-wide install. Browse the catalog at https://flatpark.org.
Add an app
Onboarding is meant to run through an AI agent. Open this repo in your agent (e.g. Claude Code) and prompt it:
I want to publish <app or upstream URL> to FlatPark. Read
CONTRIBUTING.mdand the existing PRs, then write and validate the manifest underregistry/<app-id>/.
It writes the flatpark.yml descriptor and Flatpak manifest, validates and
test-builds them, and opens a PR. If it can't get there from the rules and the
existing PRs, open an issue — letting an agent submit, test, and PR end-to-end
is the goal.
License
FlatPark's own code is MIT. It does not license the packaged applications themselves — those remain their vendors' property and are fetched from official sources at install time.