> Is there some way to incorporate vmspipe with the miniperl build, so we know
> where it should be in the build/test environment?
> >2. during MMK (build phase):
>> assume PERL_ROOT "not useful" (not defined, old version)
>> @INC search will fail, but
>> dirname($^X) should work fine.
> >
> >3. during MMK TEST:
>> assume PERL_ROOT "not useful".
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.
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.
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
