Re: Bug#29770: Policy contradicts itself about /etc/aliases
Hi,
>>"Santiago" == Santiago Vila <sanvila@unex.es> writes:
Santiago> On 2 Dec 1998, Manoj Srivastava wrote:
>> Why is this report a policy bug? I see no contradicxtion here
>> at all, I just see two buggy MTA packages. /etc/aliases, as reading
>> policy tells one, can not, and should not, be a conffile at all.
Santiago> Even if /etc/aliases stops being a "conffile", it will continue
Santiago> to be a "configuration file".
Santiago> Policy says:
Santiago> "A package may not modify a configuration file of another package."
Santiago> Please, note that it says *configuration file*, not *conffile*.
Santiago> If policy should read *conffile* instead, then please retitle the bug,
Santiago> change the severity, or whatever, so that it reads conffile and not
Santiago> "configuration file". If we do nothing about this bug, policy
Santiago> will continue to be confusing about this.
Polcy is very confused about configuration file as opposed to
conffile, and appears to use the terms inter changeably (I have
copies of a large post I made to the policy list a few months ago).
Clarifying the policy documents usage of shall, should, must,
and may, is one of the things on my plate when I get back from the
holidays. The conffile configuration file mess is another.
So, instead of closing this bug, shall I just retitle it and
propose clarification of the conffile issues? I shan't be able to
follow up until January.
manoj
--
Certainly there are things in life that money can't buy, But it's
very funny -- did you ever try buying them without money? Ogden Nash
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: