Anthony Towns wrote: > 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? I do not follow your reasoning in this last paragraph at all, and the proceeding paragraph has a flawed premise. There are more file conflicts present between potato and woody than there are in woody itself. Therefore we have to find a means to get force-overwrite turned on on upgrade. base-config cannot do that. We also seem to now want force-overwrite turned on for naive users running testing, and possibly even for naive users running unstable. The only conclusion I can see is turning it on by default in dpkg and encouraging non-naive users to turn it back off via dpkg.cfg, in the developer's reference or something. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
