Charles Lane wrote:
> Look at the problem in general: how do you find a file you need?
>
> Either (a) relative to logical (PERL_ROOT or some "special" logical)
> (b) relative to default directory (-I../lib etc.)
> (c) relative to executable ($^X)
>
> I don't think there are any other "inputs" that we can use. Even writing
> out a tempfile we'd either use the current directory or SYS$SCRATCH.
>
> If we *don't* require PERL_ROOT...and there was some sentiment that
> MMK TEST really shouldn't depend on PERL_ROOT...then we only have
> options (b) and (c)...and the testing routines don't really deal with
> those very well for reasons I outlined in an earlier message.
Just copy vmspipe.com to [.t] it is not a large file. Problem solved.
> You *could* build miniperl to use a "special" logical. But it doesn't
> get you out of the problem with MMK TEST, since the testing scripts
> use Perl, not Miniperl.
>
> In some sense testing Perl without PERL_ROOT is futile, since PERL_ROOT
> is (in practice) required for Perl to run under normal circumstances.
We also run into trouble when unixistic munging of @INC takes place
in the test suite (as happened recently with the pod tests).
Peter Prymmer
