Alexander Larsson

It shouldn't use hardlinks typically until you check something out. A single commit should not cause any hardlinks.

> It is preferable for package managers to use syncfs after writing a large number of files to calling fsync on every file. If there is a crash during this,...

This lgtm.

A bit offtopic, but how does the glib part of rgtk compare to: https://github.com/gi-rust

I can open this and then we can close it when the manpage adds more verbiage, but its not a default we can change without breaking existing users.

At least all the "Pre-Defined Annotation Keys" that has a `org.opencontainers.image` prefix in: https://github.com/opencontainers/image-spec/blob/main/annotations.md

Shelling out to `flatpak update --system` should be enough to make this work. I'm not sure how the atomic update command works though.

Its tricky to say whether it would be useful or not. It certainly pulls in a bunch of other dependencies (the portals) that are not historically always installed. I guess...

I don't think re-running it the same way and doing something else is right, but we should have a way to just connect to and wait for a running job.

Well, the garbage response is just a temporary network issue. You can reconnect to the service and get the status of the job.