As explained in a GitHub comment by a Package Maintainer, “Handling system packages via packagekit is just fundamentally incompatible with our high-maintenance rolling release distro, where any update might leave the system in an unbootable or otherwise unusable state if the user does not take care reading pacman’s logs or merging pacnew files before rebooting.”
I’m not sure it’s ever happened to me. I imagine it must have, because of Arch’s reputation, but I can’t recall it ever actually happening to me personally.
Anyway, so far all I found there is new optional dependencies.
I rather wonder what happens when manual intervention is needed, like when JDK started being in conflict with JRE.
Arch Wiki has still this warning
So its less about lack of packagekit support in pacman and more about lack of manual intervention features in GUI software managers?
it is more about arch’s philosy being your system may not boot next update, happens pretty no where else, except windows, manjaro and sometimes ubuntu
Yeah … no thanks. I’ll be okay with slightly outdated versions of various packages, as long as they still work.
I’m not sure it’s ever happened to me. I imagine it must have, because of Arch’s reputation, but I can’t recall it ever actually happening to me personally.
My last Fedora version upgrade was a test of my troubleshooting skills, for sure.
Wait, I am supposed to care about .pacnew files?
Anyway, so far all I found there is new optional dependencies.
I rather wonder what happens when manual intervention is needed, like when JDK started being in conflict with JRE.
Not right away, but they will eventually cause issues if you let them sit as
pacnew. I usemeldto resolve the conflicts and merge the two.Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/