At the Linux App Summit, Sebastian Wick, maintainer of the Flatpak tools, and Adrian Vovk, creator of the installer for GNOME OS and one of the developers of systemd-homed and systemd-sysupdate, presented a report on the future of the self-contained package system Flatpak. The report mentions an intention to create a new systemd-appd process for Flatpak, which will provide information about running instances of applications.
systemd-appd will implement functionality for assigning applications identifiers and storing permissions associated with those identifiers. The use of systemd-appd will solve issues related to reliable authentication of running Flatpak applications and determining which specific application is attempting to access system resources. Thanks to systemd-appd, nested sandbox environments will be possible (for example, for additional isolation of processes in browsers), and support for multimedia PipeWire will be established, eliminating the need for the D-Bus proxy used for filtering access to system services. server The report also introduces the Flatpak Next (Flatpak 2.0) project, which plans to redesign the Flatpak architecture based on accumulated experience and using modern technologies. Support for systemd-appd is also planned to be added to the Flatpak 1.x branch without waiting for Flatpak Next.
In response to the question of whether systemd-appd will become a mandatory dependency in Flatpak, Adrian Vovk replied that he initially intended to be very careful regarding systems without systemd, but after facing aggressive criticism that arose out of nowhere (the development is still just in planning and no lines of code for systemd-appd have been written), he does not intend to waste his time supporting systems without systemd.
In response to a similar question, Jorge Castro, community engagement manager for the FlatHub project, confirmed that systemd will become a mandatory dependency in Flatpak.
🥇Flatpak intends to make systemd a mandatory dependency | ProHoster
Source: opennet.ru
