Re: Generally fixing wrong-path-for-interpreter
On 10/19/2018 11:45 AM, Joost van Baal-Ilić wrote:
> Hi Andreas e.a.,
>
> On Fri, Oct 19, 2018 at 11:24:47AM +0200, Andreas Tille wrote:
>>
>> lots of Debian Med packages are affected by
>>
>> wrong-path-for-interpreter ... (#!/usr/bin/env perl != /usr/bin/perl)
>>
>> I usually fix this by
>>
>> override_dh_install:
>> dh_install
>> for pl in `grep -Rl '#!/usr/bin/env[[:space:]]\+perl' debian/*/usr/*` ; do \
>> sed -i '1s?^#!/usr/bin/env[[:space:]]\+perl?#!/usr/bin/perl?' $${pl} ; \
>> done
>>
>> Since this is a more general problem: Do you think it would be a good
>> idea to integrate such a code snippet into dh_perl (or any other
>> sensible debhelper tool instead of forcing single maintainers to do
>> this manually (and may be failing to do this a long time).
>>
>> Kind regards
>>
>> Andreas.
>>
>> PS: Similar things exist with Python and probably other interpreters but
>> I stumbled by far most about Perl. If you think there should be a
>> more general solution feel free to move the thread to debian-devel
>> or whatever place might seem appropriate.
>
>
> FWIW, and as yet another data point: policy 10.4 is stricter on perl than on
> python (see lintian checks/scripts.desc). Checking the policy as well as
> lintian, it seems using #!/usr/bin/env python is OK.
>
> I seems debian-devel is a better venue for this discussion...
>
> Bye,
>
> Joost
>
>
It has been discussed already:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906901
I think it's fine to ignore the warning for now.
Best,
Alex
Reply to: