Bug#598546: lintian: unsubstituted #!perl
Raphael Geissert <geissert@debian.org> writes:
>
> You would need -I,
Ah yes.
> severity
I think that check, or a part of it, should be at the normal severity
level.
If an example script has the execute bit set, but the #! interpreter is
something obviously wrong like #!/usr/local/perl or #!perl, then report
that as an ordinary error, since the execute bit means it's supposed to
be executed, but doing so will certainly fail.
An example script with an unknown interpreter could be merely info level
still, since a "#!/usr/bin/foo" might merely illustrate interoperation,
not be among the package deps. But I would think wrong stuff which is
debian "essential" or in the package deps should be reported.
I think I'd extend that rule to scripts anywhere with an execute bit
set, to catch errors maybe in /usr/lib/foo scripts or wherever.
Hmm, so a script in /bin or /usr/bin would have to have a known
interpreter. An executable script anywhere else doesn't have to have a
known one, but if it is a known one then it must be correct. Does that
sound reasonable?
Reply to: