On Tue, Dec 16, 2014 at 06:50:55PM -0500, Jaldhar H. Vyas wrote: > On Wed, 17 Dec 2014, Santiago Vila wrote: > >So: Why can't dovecot-core create the *current* file (the one *not* > >having SSL enabled) in the postinst instead of using UCF? Please don't > >tell me that you already tried that, because you have not. > > No I haven't but tell me how I am ensure that that people who have modified > that file do not see their changes get destroyed. [...]
That is quite easy indeed: * The file is not included in the package.deb. * The very first time the package is installed, the file is created from the default by postinst. * On upgrades, you do nothing at all with the file. This is even simpler than using UCF and less prone to error. The file /root/.profile is an example. Have you ever seen your changes to /root/.profile being destroyed? Surely not. And the reason is that the file is created only once, it's not inside base-files.deb and it's completely left alone on upgrades. Please take a look at base-files postinst as I suggested. And please keep this report open. I think it should be clear by now that using UCF to manage 10-ssl.conf is not a good idea, as there is not a default that will work for everybody. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
