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.”
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.
it is more about arch’s philosy being your system may not boot next update, happens pretty much no where else, except windows, manjaro and sometimes ubuntu
Arch Wiki has still this warning
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.
Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/
Yep
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 much no where else, except windows, manjaro and sometimes ubuntu
My last Fedora version upgrade was a test of my troubleshooting skills, for sure.