[arch-dev-public] keep config file on system when upgrading to package without the config file
aaronmgriffin at gmail.com
Wed Mar 17 17:55:22 CET 2010
On Wed, Mar 17, 2010 at 8:03 AM, Daenyth Blank <daenyth+arch at gmail.com> wrote:
> On Wed, Mar 17, 2010 at 06:27, Ronald van Haren <pressh at gmail.com> wrote:
>> So the new package doesn't have the config file anymore and is now
>> removing the old file (it seems it doesn't matter if the file is in
>> the backup array or not). Any way around this so I can quickly fix
>> this and people won't come in the grub shell upon next reboot ?
> I don't think this is possible internally. One because it would leave
> unmarked untracked files on /, secondly because internally an upgrade
> is a remove+install
I actually thought pacman USED to do this. If a file is in the backup
array, and it is being removed, it is moved to .pacsav. Wasn't that
the logic, or am I crazy?
More information about the arch-dev-public