On Sat, May 04, 2002 at 10:09:47PM -0400, Joey Hess wrote:
> That's a valid POV I suppose, but base-config is still not the place.
> Whatever turns force-overwrite on needs to be an essential package, so
> it is upgraded quite early, and so it is guaranteed to be installed in
> the first place. Base-config doesn't meet the criteria. The package that
> comes closest, in my mind, is dpkg...
I think you missed Wichert's point. Suppose you have a relatively
ignorant user running testing, and a developer running unstable. The
former shouldn't have to worry about file clashes, the latter should. If
whether this happens depends on whether you've got dpkg A or dpkg B
installed, there'll be a problem when dpkg B migrates from unstable to
testing and replaces dpkg A. Thus, having it done in dpkg (or any package)
as part of an upgrade isn't a working solution.
> If you want force-overwrite turned off only on request, why not default
> it to on in dpkg and then tell developers to edit dpkg.cfg and turn it
> off?
That's a good question. Maybe we should change our answer. The easiest
way to do so is by uploading a new base-config. Joey, would you object
to an NMU to do so?
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``BAM! Science triumphs again!''
-- http://www.angryflower.com/vegeta.gif
Attachment:
pgpw_979aMa5g.pgp
Description: PGP signature