I was testing a few things and was wondering about the difference between --auto-deconfigure and --unpack.
dpkg --auto-deconfigure --install P.deb
If P has a Break field such as:
and B is currently installed, then dpkg deconfigures B with a new status of "half-configured."
Similarly, you could "unpack" B first:
dpkg --install B.deb ... dpkg --unpack B.deb dpkg --install P.deb
In which case B new status is "unpacked".
However, in both cases the /etc/B.conf file stays right there. So it looks like the package is still fully installed.
My question is: Why wouldn't dpkg remove or rename B.conf? Because when I just do the --unpack the configuration file is named:
which makes sense. In that case B is really not configured!
It seems to be that the --auto-deconfigure or --unpack commands should also rename the /etc/B.conf as /etc/B.conf.dpkg-new then a --configure can restore the file as expected.
I guess that most software do not care whether a .conf exists and thus whether it is there or not doesn't make much difference in the end. Would that be the reason why they can as well leave it in place?