Craig A. Berry wrote:

> At 10:23 PM -0500 3/31/00, Charles Lane wrote:
> >
> >Avoiding dependance on having the logicals set up properly *before*
> >invoking "MMK test", sure... but MMK should be able to set up some
> >logicals that the build and test code depend on.
> 
> Isn't the problem that if MMS TEST defines or redefines PERL_ROOT and you then 
>proceed (as would ordinarily be the logical next step) to do an MMS INSTALL you will 
>be installing the build tree on top of itself rather than in wherever PERL_ROOT 
>originall
> pointed?

IIRC Charles Lane's proposed patch for adding vmspipe.com would have
added a DEFINE PERL_ROOT in terms of f$environment("PROCEDURE") to 
the descrip.mms file.  Whereas the DEFINE of PERL_ROOT in PERL_SETUP.COM
is whatever you answered to configure.com, with the default being
configure.com's idea of f$environment("DEFAULT").

In thinking back on what I posted to Charles Lane I suspect that
I was not encouriging enough: I _like_ the idea of vmspipe.com,
I like the idea of not writing temp files.  I'd just like to add it
to perl in a way that does not interfere with the updatability and
PERL_ROOT relocatability of what we already have, if possible.

Peter Prymmer

Reply via email to