ec020cd2ca
* fix:(default-flatpaks): Missing notification for system flatpaks This approach, while more fragmented, it's cleaner, as there is a clearer separation of root & non-root operations done by flatpak-setup service. This should probably increase security too (but I'm not the expert to talk seriously about that). It also gets rid of some non-harming error for /var data, can't remember it fully. While it may be confusing for users that they have to type: `systemctl status --user system-flatpak-setup` instead of previous: `systemctl status system-flatpak-setup` It is something worth sacrificing for the important user-experience fix. |
||
|---|---|---|
| .. | ||
| flatpaksync | ||
| system-flatpak-presetup | ||
| system-flatpak-setup | ||
| ublue-nix-install | ||
| ublue-nix-uninstall | ||
| user-flatpak-setup | ||