You must log in or # to comment.
We could just improve existing package managers and add sandboxing there.
I only have Flatpak installed for a single program, everything else is in the repos already. And once that one program is in there, I don’t have any use for Flatpak packages any longer. Then I’ll only have one package manager to update, not two.
This problem is reminiscent of the web-browser conundrum. Perhaps the project is, by its nature, just too ambitious to be left to a small handful of volunteers. An organization, with reputation (and maybe money) at stake, needs to take the reins.
Currently, Flatpak still uses PulseAudio even if a host system uses PipeWire. The problem with that is that PulseAudio bundles together access to speakers and microphones—you can have access to both, or neither, but not just one. So if an application has access to play sound, it also has access to capture audio, which Wick said, with a bit of understatement, is “not great”. He would like to be able to use PipeWire, which can expose restricted access to speakers only.
Oof. Seems that
snap(to take the obvious comparison) separates these two permissions. As it should.One of the big hindrances of Flatpak is precisely the dependency on PA, when both ALSA and Pipewire exist and the former has worked perfectly for over 20 years. Only way they could have made it worse was if it depended also on systemd.
Hard to believe the world’s governments aren’t all supporting open source software. Something that benefits absolutely everyone, including themselves.
