|Jeroen Demeyer on Mon, 19 Jan 2015 12:28:27 +0100|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|Re: Install Perl scripts with #!/usr/bin/env perl|
On 2015-01-19 12:20, Bill Allombert wrote:
No, it does not since the perl program checked by Configure is still used at build-time. My patch only changes things at run-time, not build-time.your proposal defeats the purpose of the Configure check, since the perl program checked by Configure might not be the perl program that will be used.
True, but that's not applicable for my patch (the scripts I am changing do not have flags). In any case, -w can be changed to "use warnings" if needed.Also, this is incompatible with the use of flags: #! /usr/bin/env perl -w
...which is true in practice. I think it's a lot safer to assume the existence of /usr/bin/env than to assume that two different systems will have the same path to Perl (especially since the default perl found in $PATH could be in some non-standard location).This is assuming that /usr/bin/env exists on the target system.