Previously Joey Hess wrote: > If the change is put into base-config, it is going to return to bother > us when we want to have plenty of unstable systems later on with > --force-overwrite turned off. If it's all done in dpkg, a new dpkg in > unstable can turn the force-overwrite off easily, but there is no > similar upgrade path for base-config.
We did think about that but decided we would rather have people make a conscious choice to toggle that flag. Normal users who track stable or testing should have it turned on, and developers and people who track unstable hould have it turned off. Note how a single file overlap now tends to result in multiple bugreports. By only letting developers disable force-overwrite the chances of such a multitude of duplicate bugreports is greatly reduced. Wichert. -- _________________________________________________________________ /[EMAIL PROTECTED] This space intentionally left occupied \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
