[PATCH] no config file overwrite for dpkg

[Kim B. Heino]

> > This patch adds new option for dpkg:
> > 
> >   By default dpkg will overwrite existing config files when
> >   upgrading. With this feature enabled new config files will be
> >   created as filename.dpkg-new.
> 
> I understand why is this useful. I wonder how "real" dpkg
> handles this? Does it have an option which enables this?
> Or does it always create filename.dpkg-new files?

Real dpkg asks user or (usually) creates dpkg-new if config file is
modified. If it's not modified it will be overwritten. My patch does
not implement this check yet. It's in my todo-list...

Real dpkg has --force-confnew and --force-confold to force overwrite or
dpkg-new. So basically current BusyBox implementation is
--force-confnew and my patch is --force-confold.