On Thu, 20 Aug 2020 at 07:10, Kusoneko <kusoneko@xxxxxxxxxxxx> wrote: > > I think he's trying to imply that pacman stores a copy of the archive > containing the previous version somewhere and that pacman should extract > the config files from both and see if something changed before providing a > .pacnew. Only thing is, that would cost much more storage space than if one > lazily ignored and let the pacnew files be wherever they're placed. In > other words, not really a good idea unless you have tons of storage space. > I guess you could theoretically patch pacman to do so for yourself if you > really wanted to, but for most people it wouldn't be worth it. I don't see what all the fuss is about If you're using Arch, then you should: 1. Check Arch news before running update 2. Update regularly 3. Watch output from pacman for warnings/advice 4. Run pacdiff after update and before reboot After step 4 there are no longer any pacnew files
