On Tue, Oct 14, 2003 at 04:17:23AM -0700, Gisle Aas wrote:
> > --- ./t/local/http-get.t-pre Thu Sep 18 23:16:02 2003
> > +++ ./t/local/http-get.t Thu Sep 18 23:16:06 2003
> > @@ -40,7 +40,7 @@ if ($D eq 'daemon') {
> > else {
> > use Config;
> > my $perl = $Config{'perlpath'};
> > - $perl = $^X if $^O eq 'VMS';
> > + $perl = $^X if $^O eq 'VMS' or -x $^X and $^X =~ m,^([a-z]:)?/,i;
>
> Why is $Config{'perlpath'} unusable on OS/2 while not on Win32?
I have no idea why it is usable on Win32. OS/2 has a concept of
$ENV{PATH} ;-), and the users may install the executable wherever they
want. In your opinion, do they need to edit Config.pm each time they
rearrange the layout of PATH?
Moreover, if Perl is not yet installed, perlpath is very wrong.
IMO, such hacks as perlpath should be used only if $^X does not work.
> Don't you want the RE to allow backslashed patches as well?
Right, it would be better this way.
Yours,
Ilya
