Talk:Pacman/Pacnew and Pacsave
.pacnew are created rarely; .pacsave created when overwriting existing files
Either I am out of my mind, or this does not work at all as described. It has been my experience that when a package replaces files it has been told to back up, it generally saves a user-modified original as .pacsave and replaces the file. I am not entirely sure what causes a .pacnew to be created, but it has been a rare occurence for me. quequotion (talk) 16:26, 14 November 2016 (UTC)
- I think you are mixing pacnew and pacsaves up - generally .pacnew files are common, while .pacsave files only turn up if you remove a package.
- See also: https://git.archlinux.org/pacman.git/tree/lib/libalpm/add.c#n319, https://git.archlinux.org/pacman.git/tree/lib/libalpm/remove.c#n501
- -- Pypi (talk) 18:55, 14 November 2016 (UTC)