On Sat, Nov 25, 2006 at 11:46:49AM +0100, Andreas Metzler wrote: > > From my reading of policy 11.6 what I'm suggesting is perfectly compatible > > (if implemented properly, which might be tricky) with having a shared > > configuration file across mail-transport-agents in Debian. > > The point is that it is not just shared among MTAs and packages > depending on MTAs.
I see. Could (maybe) exim4-config print out (when being purged) say something along the lines of "Not removing /etc/mailname as it is a shared configuration file." if he generated the file through postinst. That would at least give an indication to the sysadmin purging the pacakge that if the following is not idempotent: a) install exim4 b) configure the mail system c) purge exim4 Since the /etc/mailname generated in b) will affect a new re-install of exim4. It would had (at least) saved me one hour of debugging the issue I outlined in #400294 Either case, packages using that file (including exim4) should take care of handling bad values for /etc/mailname. Exim4 (the server) certainly does not warn the user that he is using a botch /etc/mailname when it starts. ¿Maybe it would be wise also to add a check in exim4's init.d script if he finds a botched /etc/mailname? Thanks Javier
signature.asc
Description: Digital signature
