>> In any case, this sort of hack should be left to the value of
>> $Config{startperl}
>> where it belongs, not a dozen workarounds in a dozen different projects.
>
>
> I'm not following you, how $Config{startperl} solves the problem of the
> long path, if just as you say it makes the script run under the wrong perl?
not to be dense, but I'm not really following either.
ordinarily, I'd say "fine, you get it, so go ahead and fix it" except that I
think it's important to understand exactly why perlpath doesn't work because
of this in TestRun.pm
$^X = $Config{perlpath} unless -e $^X;
so if we change to startperl across the board then we're still manipulating
the shebang - instead of adding it like we do now we'll be stripping it
here. the current situation has the advantage of being time tested, which
is why I'm hesitant to change it blindly and without a real understanding of
why startperl over pathperl mysteriously solves "the problem"
but thanks for putting up with me :)
--Geoff
