Le Mercredi 12 Mars 2003 14:39, Autrijus Tang a �crit :
> > So my question is, would it be possible to have:
>
> <patch snipped>
>
> > so that custom, non-installed version of system modules can be used?
>
> Thanks, applied, welcome to the AUTHORS file. :-)

Wow, thanks, I'm very happy to be the author of *one word* in PAR :-)))

Now if I don't find something else to fix, I will feel guilty for the rest of 
my life!

So here is something else I noticed: if you have several different perl on 
your system, say /usr/bin/perl is 5.6.1 and /usr/local/bin/perl is 5.8.0, all 
with PAR installed, building a standalone executable for the latter with 
/usr/local/bin/pp will include the wrong interpreter here:

sub par_to_exe { 
 $PARL ||= _can_run("parl$Config{_exe}") or _die("can't find par loader");
...

because of:
sub _can_run {
...
     for my $dir (split(/$Config{path_sep}/, $ENV{PATH}), 
File::Basename::dirname($0)) {

Shouldn't File::Basename::dirname($0) be first, since if you called pp with a 
fully qualified path, it probably means it's because it is not first in your 
PATH?

Germain


>
> Cheers,
> /Autrijus/

Reply via email to