The Future of Flatpak | Sebastian Wick @ LAS 2025
The Future of Flatpak | Sebastian Wick @ LAS 2025
Warning: the audio is bad and will occasionally get very loud
18 comments
-
is this available in text form?
-
Don't believe so, best that's currently available is skimming through the video to look at the slides.
Here's my short summary of the presentation, I tried to denote what's being worked on (open PR), what's kinda being done (WIP), and things stuff they'd like to be done in the future (wishlist). May be somewhat wrong.
- Flatpak is stagnant
- Red Hat is working on a better way to preinstall flatpak apps (open PR)
- Flatpak should is slowly moving towards OCI and away from ostree (more tooling available, don't need to maintain their own tools)
- Better permission handling that is more backwards compatible (open PR)
- Should directly use Pipewire instead of Pulseaudio (WIP)
- Allow user namespaces in flatpak sandbox (WIP)
- Move dbus proxying into dbus brokers (wishlist)
- Improve network sandboxing (wishlist)
- Improve drivers handling, currently drivers need to be built for each runtime, could cause issues if using EOL app on new hardware (wishlist)
- Work on portals directly improves flatpak
-
Why is it stagnant?
-
Major people of the project had moved on. It’s being maintained, getting security fixes, but pull requests are slow to be merged.
-
-
Should directly use Pipewire instead of Pulseaudio
I hope they plan on keeping pulse for the foreseeable future. Pipewire is great and all but pulse is very entrenched, I still maintain quite a bit of systems that are pulse only.
-
That is planned. But pulse is not secure, so exposing it is not great.
-
-
18 comments