On Wed, Apr 10, 2002 at 10:58:15AM -0500, Craig A. Berry wrote:
> At 09:29 AM 4/10/2002 -0400, Michael G Schwern wrote:
> 
> >    installfoo      == foo
> >    fooexp          == foo
> 
> I guess we'll just make installprefix 'perl_root' even though its 
> distinction from prefix is meaningless on VMS.  
> 
> prefixexp is already defined.  I had to make it 'perl_root:' with a colon 
> rather then just 'perl_root' because otherwise something in Installed.pm was 
> turning it into a relative path instead of using it as an absolute path.  
> 
> >    siteprefix      == prefix below which you have site_perl (which may
> >                       be just perl_root:)
> 
> OK, there is a perl_root:[lib.site_perl] (from sitelib or installsitelib), 
> so siteprefix should be perl_root:[lib] ?

    siteprefix      perl_root
    sitelib         perl_root:[lib.site_perl]

read as "the sitelib is [lib.site_perl] under the siteprefix".  The
idea being you can change the siteprefix and still have something
sensible.


> >    sitebin         == siteprefix + directory where binary programs from CPAN
> >                       modules should go.
> 
> installbin is currently just perl_root:[000000].  We should probably make 
> sitebin the same as sitearch (sitearch='perl_root:[lib.site_perl.VMS_AXP]') 
> for those rare installations where a VAX and an Alpha share an installation 
> directory tree.

Err... you sure you want to install programs into lib/site_perl/VMS_AXP?


> >    vendor*         == don't worry about them.  If configure.com doesn't
> >                       support them, just leave them blank and set
> >                       usevendorprefix to ''.
> 
> Zero-length string, not undef?

I like '' instead of undef because undef, while technically false,
really means "this value is not defined" in the terinary logic sense.

'' says "Yes, I did think about this and its supposed to be false"
whereas undef suggests "maybe it's false, maybe I forgot to ask, maybe
this Config.pm is broken, maybe this Perl is too old to know about
vendor targets.  Dunno."

Meanwhile, back in the real world, it means I can do: 

    if( $Config{usevendorprefix} ) { ... }

and not get a 'use of uninitialized value' warning.


-- 

Michael G. Schwern   <[EMAIL PROTECTED]>    http://www.pobox.com/~schwern/
Perl Quality Assurance      <[EMAIL PROTECTED]>         Kwalitee Is Job One
Don't treat people this way!  Milk & Cheese are indestructible!  You are not!

Reply via email to