control: tag -1 +patch Hello,
I am seeking seconds for the following patch to close this bug, which I
think is uncontroversial at this point.
> @@ -185,7 +185,7 @@ All command scripts, including the package maintainer
> scripts inside the
> package and used by ``dpkg``, should have a ``#!`` line naming the shell
> to be used to interpret them.
>
> -In the case of Perl scripts this should be ``#!/usr/bin/perl``.
> +In the case of Perl scripts this must be ``#!/usr/bin/perl``.
>
> When scripts are installed into a directory in the system PATH, the
> script name should not include an extension such as ``.sh`` or ``.pl``
~~~~~
As has been pointed out by Gian, there is a broader issue of whether it
is right for Policy to say
Perl programs and modules should follow the current Perl policy.
or
Perl programs and modules must follow the current Perl policy.
I think this is actually quite tricky: if packages must follow the Perl
policy, does that erase the difference between 'should' and 'must'
requirements in the Perl policy?
If someone thinks it is a big deal that Policy says only that packages
should follow the Perl policy, and is willing to do the work to handle
these complexities, they should file a new bug against Policy.
Otherwise, let's put that broader issue aside and just fix this
confusing inconsistency about shebangs.
--
Sean Whitton
signature.asc
Description: PGP signature
