DISCLAIMER: Arch Linux is not a beginner friendly distribution, and this is not a recommendation or good practice.
I know how to use pacman -S. I have yet to experience a Discover related issue after months of use.
DISCLAIMER: Arch Linux is not a beginner friendly distribution, and this is not a recommendation or good practice.
I know how to use pacman -S. I have yet to experience a Discover related issue after months of use.
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 much no where else, except windows, manjaro and sometimes ubuntu
My last Fedora version upgrade was a test of my troubleshooting skills, for sure.
Yeah … no thanks. I’ll be okay with slightly outdated versions of various packages, as long as they still work.
I mean I’ve been running an arch derivative for nearly ten years and the last time I got got was an Nvidia driver bug in 2020.
As much as arch talks about it it doesn’t happen that often.
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.
Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/
Yep
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.
This comment should be deleted soon
meld makes the task less annoying +1