On Sun, Dec 25, 2005 at 03:24:21AM +0800, Uwe Dippel wrote: > This is bad news. The reasoning is flawed from the start: > 1. There is no hint that /usr/share/postfix/main.cf.dist would be the > original main.cf. And it even isn't. How to know ?
well, except for these lines at the start of /etc/postfix/main.cf: # see /usr/share/postfix/main.cf.dist for a commented, fuller # version of this file. > 5. dpkg-reconfigure - if it is to make any sense at all - would have to > cater for this highly subjective behaviour of Debian's postfix and more debconf questions would only make it worse... As it is, if you edit main.cf after running debconf, it has to pick up your new answers as the defaults, lest you change things when you just hit return... > Once again: To offer *additional* explanations and examples are fine. > But these do not warrant to remove the original files from the > underlying sources with which most of the users are familiar and > replacing these with arbitrary partial collections without any > explanations. Nor does cluttering up a file with useless things like manpages in the form of comments. > Examples here: What use would these parameters in main.cf as provided by > Debian have say to the average user ?: The things in /etc/postfix/main.cf are the sum total of things that debian has changed from the upstream defaults. Everything not mentioned in the file is the upstream default. That is, if you take the debian sources, and compile them on a non-debian system, you get the (expected) upstream behavior. > Instead something like this would belong into main.cf: > ># Debian GNU/Linux specific: Specifying a file name will cause the > ># first line of that file to be used as the name. The Debian default > ># is /etc/mailname. > ># > >#myorigin = /etc/mailname > Who is going to *think* of this or find it in 25kByte of that That probably does belong in our main.cf. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
