Bug#217589: dpkg: --force-noovewrite option, for not replacing existing files.
On Fri, Mar 18, 2005 at 02:34:33PM +0000, Scott James Remnant wrote:
> Rejected.
>
> You can either:
>
> 1) divert files that you intend to deliberately replace.
>
> 2) add a Replaces: to the installed package on the one you wish to
> install, so the one you wish to install only installs files that
> differ.
>
> dpkg has no need for an "only install part of a package, randomly"
> option.
>
I think you miss the point, try reading my message again.
1. I don't think unpacking and repacking a deb is as easy as "mv; dpkg
-i; mv;".
2. I still don't think this works for this case. Would "Replace:
lilo" cause these files to be saved? The files I'm talking about are
'cruft' and not in the pkg database. They are the correct files and
should not be deleted. Think in terms of kernel modules, you
wouldn't want upgrading your kernel(from 2.6.10-1 to 2.6.10-2) to
mess with your DRI kernel driver.
I know it's confusing but the default is to not overwrite pkged files,
unless they belong to you. What I'm talking about goes one step
further, to save files that don't belong to any one. Think "cp -i",
install(1) is missing this feature so I can see where your attitude
comes from. This seams like an important feature for debian and I can
see multiple uses.
> Scott
> --
> Have you ever, ever felt like this?
> Had strange things happen? Are you going round the twist?
--
/*********************************************************
* Mike Mestnik: Support Technician 612-395-9010 *
* support@visi.com Visi.com *
*********************************************************/
Reply to: