Never used it, but I’m fairly sure you can’t have conflicting dependencies with pacman. If package A requires a new dependency version and package B requires an older one you can’t have both installed
This can happen and it’s usually solved by just introducing a new package which is the old version of the package, and which won’t be updated.
But this isn’t really the aim of Arch. I’ve never had this issue except for with Spotify when installed via pacman, and then only needed it to get playback of local music files.
After I switched to installing it from Flatpak, it included all the necessary packages with correct versions (obviously, because that’s how Flatpak works).
But as I said, the aim of Arch is to support working, latest versions of software. If you want to be able to roll back stuff, Arch is probably not for you, even if it’s very simple to roll back stuff if you have the package file on disk or it’s still available in the remote package repo. But if this is something you often come across, sure.
You need them like you need fire extinguishers
My Ubuntu LTS upgrade failed. Would have killed for a rollback
You need fire extinguishers if you have something worth saving.
Sometimes I just want to roll back one piece of software. Try doing that with flatpak
Wouldn’t
flatpak uninstalldo that? Or what do you mean “roll back” in this case?Uninstall uninstalls the package. I want to use an older working version
Ah. Well, that’s simple with pacman. 👍
Never used it, but I’m fairly sure you can’t have conflicting dependencies with pacman. If package A requires a new dependency version and package B requires an older one you can’t have both installed
This can happen and it’s usually solved by just introducing a new package which is the old version of the package, and which won’t be updated.
But this isn’t really the aim of Arch. I’ve never had this issue except for with Spotify when installed via pacman, and then only needed it to get playback of local music files.
After I switched to installing it from Flatpak, it included all the necessary packages with correct versions (obviously, because that’s how Flatpak works).
But as I said, the aim of Arch is to support working, latest versions of software. If you want to be able to roll back stuff, Arch is probably not for you, even if it’s very simple to roll back stuff if you have the package file on disk or it’s still available in the remote package repo. But if this is something you often come across, sure.
You can roll back if you have the older version on disk if you didn’t install newer dependencies that make them incompatible with your system
I have this issue with sysd manager, the characters are all boxes in the latest flatpak
Nix installs the deps separately if they are different versions and lets you install any version, even some ancient one