Charles Lane wrote:
> I'd like to see CONFIGURE.COM build a COM file that contains the
> commands needed to build/test/install/tidy/clean Perl.
>
> You should be able to just "submit" the com file with appropriate
> parameters.
>
> Something like:
>
> BUILD_PERL.COM:
> -----------------------
> $ define/trans=conceal PERL_BUILD_ROOT disk4perl:[wherever.perl.]
> $ set default PERL_BUILD_ROOT:[000000] !! avoid 8 level depth problems
> $ define PERL_MBX_SIZE 256 !! for tests, avoid quota problems
> $ mms/macro=(__DEBUG__=1) "''P1'" "''P2'" etc !! << substitute appropriate line
> $ exit
>
> Configure would generate the definition of PERL_BUILD_ROOT and
> insert an appropriate MMS/MMK line for builds.
>
> Then you can just @BUILD_PERL, or better yet SUBMIT BUILD_PERL
> and go get a cappuchino while it runs.
>
> Just a simple little feature that'll be trivial to implement and make
> users happy!
OK. One thing that'd be helpful is to check the acceptability of
the result of C<$ MMS test>, which would imply setting a global
exit $status from test.com I would think. A conservative approach
would be do not proceed with C<$ MMS install> if C<$ MMS test> is
not 100% OK.
Another minor implementation detail is that for folks who choose
to take the "put a perl in DCLtables" route the BUILD_PERL
would require full privs. Down that path lies a full re-implementation
of SYS$UPDATE:VMSINSTAL.COM - shudder.
Let not such naysaying impede progress though. I do agree with
the desirability of this feature request.
Peter Prymmer
