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. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
