Le 24/08/2012 11:21, Thierry Vignaud a écrit :
On 24 August 2012 11:11, Guillaume Rousse <[email protected]> wrote:
By calling /usr/bin/perl directly...
What? I don't understand. Do you mean that the Perl programs should have
"#!/usr/bin/perl" as their sha-bang? (Which will require either
postprocessing them or tweaking their installer.)
Yes, packaged perl programs should use an unversionned shebang, which is
the case for the large majority of them.
We could clean that in spec-helper.
Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
Yes, it seems a marvelous idea to automatically convert python and tcl
scripts to use perl interpreter instead, it will make our base installation
footprint lower :)
More seriously, we can do it easily for perl and tcl, but with much caution
for python, as we have two different major versions available at once in the
distribution.
Let's say we should do it for perl/php/tcl for now
Actually, it seems a bit exagerated to add yet another script for
spec-helper that will scan all text files for all packages at each
build, in order to solve such low occurence issue... How many packages
are concerned ?
--
BOFH excuse #48:
bad ether in the cables
