This happens whenever I upgrade kdebase-workspace. Shouldn't there be a backup file with my modified version created by pacman upon upgrade?
pacsave/pacnew files are only for configuration files that the maintainer can predict may be edited by the user. You can request that they add the file to the backup array in the PKGBUILD, or just remember to replace the file after upgrading.
Last edited by Scimmia (2013-01-15 20:12:53)
You could add the file to NoUpgrade in pacman.conf.
That is a good idea, thank you! Also thanks for the pointer to the backup array, didn't know how the .pacnew / .pacsave thing worked internally.
My modifications to that file are for pam_ssh single sign-on loading of my ssh-key, btw. So it's not critical but annoying having to re-edit that file again and again - especially since kdebase-workspace is updated quite frequently.
Is that a kde-specific change? Or could it be done elsewhere under /etc/pam.d/ , i.e. in a file that gets pacnew'd?
It could be done elsewhere I guess, but I don't want this to happen when i login to a normal console. I consider this a higher-level thing which I want only to happen if I login into a desktop environment...