Adapt or Die How new Linux packaging approaches affect wider KDE
summary
Argues that containerized app delivery via Flatpak runtime+sandbox fundamentally changes security, plugins, styling, dev setup and library policies; demonstrates a concrete developer win where Builder opens an app plus all dependency sources instead of wasting a day chasing ABIs; warns immutable OSes (Silverblue, Fedora variants, Ubuntu Core) make store availability mandatory; lists concrete breakages and fixes: system tray needs org.kde.StatusNotifierItem permission, KConfig globals and KWallet need portal redesign, KRunner runners work after a two-line Flatpak change, and sccache sharing builds plus thumbnail sandboxing merged to Kira are practical wins.
AI-written summary · about
chapters (19)
- 0:00Introduction to packaging changes
- 1:11Moment of enlightenment on sandboxing
- 3:51Sandboxing expectations and user trust
- 5:23ABI flexibility and reproducibility
- 6:54Containerized builds and caching
- 7:41Immutable distributions pressure
- 9:14Requirements for KDE on immutable systems
- 10:21Current state of KDE packaging
- 11:08How Flatpak sandboxing works
- 14:16Designing frameworks for Flatpak first
- 15:00Case study system tray icons
- 17:12Case study KConfig handling
- 19:25Case study KWallet integration
- 20:54Case study KIO in Flatpak
- 22:35Restructuring KDE Frameworks
- 25:15Plasma integration challenges
- 27:53Case study KRunner extensions
- 30:43Plasma applet and module sandboxing
- 33:28Q&A and future directions
related talks
10mFlatpak Flathub and KDE: A Quick Summary
01h 00mApps on the linux desktops
31mUnsung Hero Of the Cloud Native Revolution: Container Linux Then And Now
03h 02mDay 1 - Room 2 Session 2
30mBuilding Linux Distributions for Fun and Profit
48mPanel Discussion: Do One Thing, and Do It Well: Special Purpose OSes Apply the Unix App Philosoph...
26mContainerize your Primary Workstation! - Fedora Silverblue
01h 25mSandboxing a Linux Application