On Tue, 31 Jul 2012, Josh Triplett wrote: > Consider the original motivation for this. You have a package A, which > contains a daemon B and an init script /etc/init.d/B. You split B and > its init script (and any other configuration files for it) into its own > package, which A does not depend on. If installing B, you want to > preserve the configuration of B. B didn't exist beforehand, so no > package exists for A to declare a Breaks against. However, nothing > guarantees that the user will install B at the same time as upgrading A. > In particular, it seems highly likely that a user who wants B will > upgrade A, read the NEWS.Debian file, and then choose whether to install > B.
OK so we really need a "recover_conffile" which would be used in package2 and would move a .dpkg-bak copy in its original place. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
