flatpak-docs VS transactional-update

You can install flatpak-builder on SteamDeck with flatpak install org.flatpak.Builder. After that, you can follow the official documentation. Just use flatpak run org.flatpak.Builder instead of flatpak-builder .

Here's the PR: https://github.com/flatpak/flatpak-docs/pull/345 And the issue: https://github.com/flatpak/flatpak-docs/issues/342

/etc/fstab is the only special case, because it needs to be in sync with the overlay IDs. One can see this by looking at Overlay.cpp iand how fstab needs to be handled there.

So the way it would work out in Ansible, is that someone would need to write a module such as this rpm-ostree module: https://gist.github.com/dustymabe/926c0d9bb998b1404b9bc55021977fb7 where instead of calling rpm-ostree, it would call the transactional-update command.

A more efficient and reliable approach is to install the updates in a system snapshot and just boot into that the next time the system is started, which is what transactional-update does. openSUSE MicroOS goes a bit further even and the system volume is mounted read-only to prevent even accidental changes to the running system. The installation DVD comes with a Plasma option which is currently markes as Beta, testers are welcome!