[EMAIL PROTECTED] 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.
I'd recommend writing a perl script or DCL procedure that does the editing.
At the very least make the relocatable perl_setup.com a non default option
offered by configure.com.
It is implemented as a slightly hidden non-default option.
For CGI scripts and other advanced setups obviously there are better
ways of doing it, by using the JOB, GROUP, SYSTEM or custom tables.
I just discovered that the *.OPT files in the build directory have
absolute pathnames in then, and the ones in the directory created by the
install step have absolute files.
It gets me curious of why not simply use logical names in the option
files, and use $define/user or $define in the build procedure.
-John
[EMAIL PROTECTED]
Personal Opinion Only
