On Thu, 10 Aug 2000, Prymmer/Kahn wrote:
> Greetings,
>
> The latest round of updates to configure.com have recently been
> posted here at best:
>
> http://www.best.com/~pvhp/vms/cfgperl_6529/
Please see also:
http://www.best.com/~pvhp/vms/cfgperl_6602/
The configure.com7 configure.com replacement has been tested by
me with the 6529 kit but not the 6602 kit (yet anyway) so I don't
yet know what patches/updates have been applied to the 6602 kit.
Regarding BUGS that I had in configure.com6 and their status in
configure.com7:
> BUGS:
>
> archname gets written twice to config.sh.
This is now fixed.
> Should gidformat contain " characters? It appears to be:
>
> gidformat='lu'
I left this one as is and noticed at least one other format that does not
have double quotation marks in it (pidformat ? or something).
> The prefix mess is a bug.
I now write out to config.sh the value of prefix via:
$ WC "prefix='" + prefix + "'"
and noticed almost no trouble (except possibly a little glich in
`mms install` that is discussed below).
> The RCS variable should be considered a bug until I can get
> a hold of a perforce guru.
I removed the RCS style variables such as $Date, $Author, etc.
> MORE TODO:
>
> The procedure does not yet check for nor attempt to write a config.com.
>
> The procedure does not deal with a prior config.sh at all.
As I mentioned in a previous message configure.com;7 now handles a
"-f<filespec>" argument (though not well) or a config_sh==filespec global
symbol where the filespec must be relative to [.UU] so for example:
config_sh == "[-]config.sh"
@configure
is one way to specify a file that will be @ executed from DCL. Which
means that is ought to be DCL global symbol assigment syntax rather than
shell variable assignment syntax. Note of course that the config.sh that
gets produced by configure.com is shell syntax. In order to convert a
configure.com produced config.sh file to DCL syntax you can try something
like the following (assuming you have a perl at hand already built):
$! This @ is why config_sh must employ DCL syntax. Note that for
$! symbols to be returned to this procedure they must be global.
$! Which implies that assignments must be of the :== or == variety.
$! Note further that the [-]config.sh file written by this procedure
$! employs shell syntax. In order to convert shell syntax to DCL
$! you might try:
$!
$! perl -ni -e "s/^#/!#/;s/='/==""/;s/'$/""/;print ""\$ $_"";" config.sh
$!
$! However, watch out for sig_nam, sig_nam_init, sig_num, startperl
$! and any of the lower case double quoted variables such as the *format
$! variables in such a config."sh".
$!
$ @'config_sh
And I note that the double quotish variables such as this in shell
uvuformat='"lu"'
will be converted by that one-liner to:
$ uvuformat==""lu""
which results in the symbol uvuformat having the value "LU" rather than
"""lu""". However, as before uvuformat is not one of the variables that
is checked for prior existence by configure.com;7.
> Try to have only a config.sh file rather than a config.sh and a config.local
> files for the interactive editing option.
This is done in configure.com7
> The procedure does not check the user specified prefix:
> device mounted?
> directory exists?
> write directory if it does not exist?
> test and warn about writability?
>
> Should we even consider MAXBLOCKS tests of the destination filesystem?
I meant FREE, at any rate these tasks are not yet done in configure.com7
> The procedure does not check the PGLFLQUO of the initiating process
> against a minimum value (100000?).
This is done. As mentioned in a previous email message the variable
pgflquota now gets written to config.sh hence to Config.pm.
> MORE TESTING:
>
> Does "-M" still work? Does a "-des" config.sh have all the
I meant "-m" and yes it still works.
> Does "-M" still work? Does a "-des" config.sh have all the
> same installation paths that an interactive configure has as well as
> an interactive configure where the user opts not to skip the
> remaining "where install" type questions but does wind up taking all
> the defaults. Does `mms install` work? Do extra modules install?
I have only had a chance to test configure.com7 with the 6529 kit
and with it I was able to config with:
@configure "-m" "-Dprefix=dkb100:[perltest.]"
and I was able to do an `mms install` with that configuration. The only
hitch encountered was this one:
mkdir /perl_root/lib/vms
cp dclsym.pm /perl_root/lib/vms/dclsym.pm
chmod 444 /perl_root/lib/vms/dclsym.pm
cp filespec.pm /perl_root/lib/vms/filespec.pm
chmod 444 /perl_root/lib/vms/filespec.pm
cp stdio.pm /perl_root/lib/vms/stdio.pm
chmod 444 /perl_root/lib/vms/stdio.pm
Can't cd to (./) user : no such file or directory
which seems to be more of an installperl glitch rather than a prefix
glitch. The resultant installed perl_root is capable of adding some more
modules as reported in previous email messages.
Peter Prymmer
