Michael Schwern wrote:
!All I know is $Config{installprefix} is where perl got installed and
!$Config{installsiteprefix} is where additional CPAN modules get
!installed. Unless I'm misinterpreting the Config.pm docs, which is
!entirely possible.
Based on these comments I suspect you are misinterpreting
installprefix as far as the perl Configure -> config.sh
(hence Config.pm) is concerned.
Note that with a perl@15814 kit on Solaris I see these:
% cd perl
% grep installprefix installperl
% grep installsiteprefix installperl
In other words those %Config variables do not
enter into the installation of perl (at least not
directly, they do enter in if you were to:
`sh Configure -Dinstallprefix=/one/loc -Dprefix=/another`)
installprefix is used as an intermediate directory
into which a built perl kit can get tossed so as to
allow cleaner use of tar (or pax, or cpio or what have you).
It is completely unneeded on VMS, and could in fact
lead perladmins astray doing unnecessary things.
op cit: C<=head2 Creating an installable tar archive>
in the INSTALL file that ships with perl.
My previous comments pertained to a flaw in the
implementation of perl's $Config{installprefix}
that, if fixed, could make things a bit easier
for Unix perladmins but would still do little for
VMS perladmins since we still would not need to
even use the installprefix mechanism. I am sorry
if my previous post sounded a bit grumpy or irate.
Peter Prymmer
