Flatpak Flathub and KDE: A Quick Summary
summary
Flatpak shifts build responsibility to app authors but KDE supplies a kd runtime and SDK so apps skip rebuilding KDE Frameworks; apps need a manifest and are built with flatpak-builder (plus hashes and flags) and then published to a remote. Flathub is the default remote so discoverability matters; KDE has around 50 applications on Flathub versus ~200 on k.org, and Okular shows about 35,000 downloads. Runtimes use freedesktop-sdk and sandboxing causes some access problems.
AI-written summary · about
chapters (8)
- 0:00Introduction to Flatpak
- 1:51KDE Runtime and SDK
- 3:56Building Flatpak Manifests
- 5:22Flatpak Remotes and Flathub
- 6:46KDE Apps on Flathub
- 8:14Future of KDE on Flatpak
- 9:17Technical Challenges
- 9:58Closing and Q&A
related talks
41mAdapt or Die How new Linux packaging approaches affect wider KDE
01h 00mApps on the linux desktops
32mWhy and How to Use KDE Frameworks in Non-KDE Apps
11mKDE to Make Wines — Using KDE Software on Enterprise Desktops a Return on Experience
27mKDE neon
22mRunning virtual machines in the Flatpak sandbox
16mBuilding Flatpaks from Fedora RPMs
40mAn Operating System of Our Own