If I use a non Arch distro → flatpak for me. Snaps are a deal breaker. I won’t use them unless all other options no longer exist.
If all other options no longer exist, likely Linux won’t either. Complete Armageddon, or I’ll have already been retired and the only package manager I care about is the chick behind the bar packaging up my Margarita.
Truth is, AUR is what keeps me locked in into the Arch eco-system. As close to the metal as possible (meaning as little packaging as possible compared to snaps or flatpacks for example) while offering the widest range of software. I liked Suse Tumbleweed and stuck with it for a while, but the limited software variety just made it a no go in the end.
Many arguments are easier, faster and more comfortable.
But that is exactly the argument of the common Windows user. They should be animated to switch to linux and to have it easy with it. That’s why all the crap is build in. I do not like the increasing windowization and it makes me worry.
I saw ALPM and it didn’t register at first. So i was looking some things up. I just wondered does Arch or EOS have a hook like this?
# Force disks to sync to reduce the risk of data corruption
[Trigger]
Operation = Install
Operation = Upgrade
Operation = Remove
Type = Package
Target = *
[Action]
Depends = coreutils
When = PostTransaction
Exec = /usr/bin/sync
Edit: Sorry if it’s off topic!
Edit2: I just wondered if it’s part of pacman?
I don’t believe so. I also can’t think of any reason you would need to do that. I mean, how could that actually cause corruption? If you are waiting your update to finish and immediately pull the power cord out?
It depends how you configure your fstab. Default is for example write to cache into ram (if files smaller as ram cache). And after that to write it to the disk. But today most people didnt notice this because the most have ssd or nvme disks (and 8gb or more RAM). So, if your shutdown directly after updating for example, it could happen that your installation gets corrupted (but most likely only on slow systems on hdd).
You could add data=writeback to fstab, to prevent this entirely. than everything gets directly written to disk.
Yeah. Should But it could exist 305232793 Scenarios where this didnt happen.
Like always, it depends what somebody wanna do. If you wanna be 100% save that no single corruption could occur, than disable caching and enable writeback. And switch to a whole other Filesystem anyway. But for normal Desktop usage. “Should” is good enough.
If the outcome is what can be observed watching appimage, flatpak and snap, I’d honestly prefer them staying with Windows. This happens, if companies or developers start caring about what people want. The aim of Linux never was to catch as many Windows or Apple users, as possible. Maybe they should stop user hunting and just go back to the roots.