Craig A. Berry wrote:
At 6:43 PM -0400 7/11/05, John Malmberg wrote:
Perl_setup.com is optionally built such that it defines perl_root
based on the directory it currently resides in, as a step toward
>> being able to build a binary distribution kit that does not require
editing it.
It has bothered me for a long time that we create a perl_setup.com
that cannot be distributed and used as a smart set-up procedure that
deduces its own location and sets perl_root accordingly. When I
distribute binaries, I do this, but it's not in the core for the
following reason.
The problem with creating a smart perl_setup.com is that the
installperl script, via the install target in
[.vms]descrip_mms.template, uses it to figure out the target
installation directory. So if we have a self-locating
perl_setup.com, we'll just be installing on top of the source
directory. Probably the right thing to do is rewrite the install
target so it does not depend on perl_setup.com to know where it's
installing.
Yep, I encountered that too.
If you look at the Perl_setup.com that is optionally generated, if that
same logical name is present that triggers the optional Perl_setup.com,
it also inhibits Perl_setup.com from overriding the logical name
Perl_root in when the install step is done.
There are other things that need to be set at installation time that
Perl is currently setting at build time. Things like the contact
information and e-mail addresses.
Also it appears that some want Perl to report the current OS version
instead of the OS version that Perl was built on or installed on. By
default Perl reports the OS version that Perl was built on.
-John
[EMAIL PROTECTED]
Personal Opinion Only
