At 12:18 PM -0800 2/12/01, Peter Prymmer wrote:
>However, if you build and install like so:
>
> $ set def dka200:[perl-5_6_1-trial2]
> $ @configure "-Dprefix=dka100:[perl-5_6_1.]" "-des"
>
>then running `mms install` will place the perl installation tree into
>dka100:[perl-5_6_1...] and write out a perl_setup.com procedure that
>defines the PERL_ROOT logical name to be dka100:[perl-5_6_1.].
Good reminder. Is there a pod somewhere that documents all of the
options that can be fed in as command-line parameters? When creating
pre-built kits it would be particularly helpful to configure the Perl
administrator as 'system' instead of having the builder's e-mail
address appear for every installation that uses the pre-built kit.
>The advantage of going through the extra hassle of specifying the
>"-Dprefix=dka100:[perl-5_6_1.]" parameter to configure.com is that all of
>the intermediate file detritus: *.OBJ;, some *.OLB;, *.OPT; etc. files
>will not be installed into dka100:[perl-5_6_1...] and the tree will be
>smaller.
Yup, about half the size on Alpha.
>The disadvantage is that one cannot then run the `mms test` IVP
>except for in the dka200:[perl-5_6_1-trial2] directory owing to relative
>file specs within many (but not all) of the tests (particularly those in
>[.T.LIB]*.T and [.T.PRAGMA]*.T).
Ah, but if we dump the contents of [.t...] from the build tree into
the installed tree (perl_root:[t...]) as part of the install, won't
all the relative dir specs work out, including [-.lib]? Then the
tests could be run from there, and the installation could finish up
by deleting perl_root:[t...]*.*;*. There might be tweaks to
[.vms]test.com, including figuring out where in the install tree to
put it, but I don't think it should be a major rewrite of the whole
test concept.
Remember, the problem is not that Hoff needs help testing Perl on his
own machine, but that someone using the PCSI kit he's built (and
knowing nothing about Perl, MM(S|K), etc.) could get a reasonable
indication that s/he has a working Perl installation.
--
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
