Bug#403391: debian-policy: scripts as configuration files: should vs. must
Jörg Sommer <joerg@alea.gnuu.de> writes:
> Hi Russ,
>
> Russ Allbery schrieb am Sun 16. Mar, 15:01 (-0700):
>> Russ Allbery <rra@debian.org> writes:
>>
>> > Here is the patch that I'm applying. If anyone objects, yell now.
>>
>> Actually, looking at this further, I see the Policy was never updated to
>> mention the /etc/cron.hourly directory. I'm fixing that as well. Here's
>> the new combined patch.
>>
>> --- orig/policy.sgml
>> +++ mod/policy.sgml
>> @@ -6388,12 +6388,13 @@
>> + treated as configuration files. In general, any script that
>> + embeds configuration information is de-facto a configuration
>> + file and should be treated as such.
> ^^^^^^
>
> Wasn't the initial request that these files /must/ be configuration
> files?
Specifically that the ones mentioned earlier in that paragraph must be,
since that's what the release notes call out. The general Policy
statement is far more broad, and I don't think Frank was proposing that
change, only asking that Policy be consistent with the RC bug policy which
calls out all cron jobs and init scripts.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: