Mass-filing bug against use of '/usr/bin/env perl' shebang line
I'm looking for some advice about filing a (more or less) mass-bug
report against perl scripts using /usr/bin/env in the shebang line.
First of all, the proposed template:
One or more perl scripts in your package use the `#!/usr/bin/env perl'
Perl policy §5.1 states:
"All packaged perl programs must start with `#!/usr/bin/perl' and may
append such flags as are required."
The rationale behind this statement is that a perl script shipped within
Debian has its dependencies fulfilled via the package manager. This
cannot be guaranteed if the perl environment interpreting it is not
itself shipped via Debian.
When using `#!/usr/bin/env perl', the script is interpreted by the first
perl binary found in the $PATH of the user, so there's no guarantee this
is the perl binary shipped by Debian. For example, when enabling a
custom environment managed by perlbrew, the user could be forced to
re-build and re-install the needed modules for every perl version he has
installed via perlbrew.
Please change the shebang line for the following script(s) in order to
be compliant with the Perl policy:
Now my questions:
Report. Do you think the above template is suitable for filing the bug
Severity. I think it should be serious, as it's a violation of a policy
`must' but I'm someway uncomfortable with it, especially during a
freeze. OTOH, it's trivial to fix and I'd prefer the fix to be shipped
with wheezy. Do you think 'serious' is appropriate?
Usertags. Would you prefer the reports set some specific usertags and in
that case is it appropriate to use the debian-perl list address?
As reference, attached there's a list of such scripts installed on the
pc I'm writing from.
$ head -n1 /usr/bin/* /bin/* 2>/dev/null | egrep -a -B1 '#!\s*/usr/bin/env\s+perl' | perl -nE '( $f ) = $_ =~ m|==> (.+) <==| or next; say $f' | xargs dpkg -S | sort