On Wed, Apr 10, 2002 at 09:38:10AM -0400, [EMAIL PROTECTED] wrote:
> I would advise against doing any thing with installprefix, possibly
> with the other /^install\w+/ variables as well. They are of use
> primarily on Unix where you do not have binary relocatability
> of perl (on non Unix, including VMS, we have binary relocatability).
Even if installfoo == foo they should still be there.
prefix means "here is where I will be run from"
installprefix means "here is where I will be installed"
and the same for the rest of the install* variables. On VMS they just
happen to always be the same. They're the same on most Unix
installations, too. And that's correct.
Even if prefix & installprefix are the same, you still use
installprefix to install things and prefix to run things. This frees
users from having to worry about weird installations.
Same for the *exp variables. On VMS they're just going to be the same
as the normal variables (unless you have things in paths that can be
"shell" expanded?) but they have to be there.
Else you wind up with code like:
$prefix = $Config{installprefixexp} || $Config{installprefix} ||
$Config{prefixexp} || $Config{prefix};
trying to guess where we should get the prefix from. And that's
unfortunately what MakeMaker's going to have to do to support 5.6.1 on
VMS.
As it stands right now VMS's %Config is inconsistent. It has things
like installarchlib and installprivlib but no installprefix from which
they were derived.
So if you just do the logical equivalent of:
installfooexp = installfoo = fooexp = foo
(where applicable) you should be ok.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
come sing my fun song
my bologna has a first name
p a s t e
-- Fmh
