Re: New dpkg overwrite behaviour undesirable
warwick@cs.mu.OZ.AU writes:
> Andrew Howell <andrew@toaster.it.com.au> wrote:
> > Well the whole point of that behaviour is so files don't get overwritten.
> > I agree it would be better if it just warned you about the file and didn't
> > overwrite it, but continued on with the rest of the files instead of
> > bombing out. But this shouldn't really be a problem once we have discovered
> > all the packages that conflict with each other and either got rid of the
> > conflicting files or added Replaces field to them.
>
> Please re-read what I wrote. My whole point was that *even if* we have
> fixed all such conflicts, dpkg can still have problems - when upgrading past
> the point where it was fixed. We're supposed to (eventually) be offering
> easy and smooth upgrade from 0.96R6 to 1.1 - with dpkg the way it is now,
> *every* system with manpages installed will fail with these problems on
> upgrade.
Good point, well then it should work like I said, instead of bombing out
at that file it should just give a warning, not overwrite it, and continue
onto the next file in the package.
Andrew
--
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%. Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
-- Kryten in Red Dwarf `The Last Day'
Andrew Howell andrew@it.com.au
Perth, Western Australia howellaa@cs.curtin.edu.au
Reply to: