Re: First draft of review of policy must usage
Luk Claes <luk@debian.org> writes:
> Otavio Salvador wrote:
>> Manoj Srivastava <srivasta@debian.org> writes:
>>
>>>> @@ -6736,10 +6654,10 @@
>
>>> This flows from the Release policy. Not specifying /bin/bash
>>> in scripts is not considered a RC bug.
>>
>> Oh Gosh! This _is_ a RC bug. If I change the /bin/sh to point to
>> /bin/dash (and I usually do that) some script will break and this
>> cannot happen since they said, when defining their shell as sh, that
>> they're using just POSIX functionality.
>
> Indeed, it's a bug, though it's not release critical yet...
>
>> That kinda of change in policy can decrease the overall quality of
>> packages. Release policy is _wrong_.
>
> It's an important bug and might become release critical after etch...
>
> I don't think it's a good idea to change the policy manual for every release
> to match release RC policy. In current policy it's clear that it's a bug that
> should be fixed in the package and I'm sure it will become release critical in
> a next release...
Well, AFAIK when you say that it uses just POSIX features and it's
part of the core functionality of package (init scripts, for example)
it's a RC in my POV since it makes the package useless. We can't force
the user to use a specific shell if we don't enforce it on the script
header.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
Reply to: