--- David Golden <[EMAIL PROTECTED]> wrote:
> > $ROOT/lib/
> > $ROOT/arch/lib
> > $ROOT/bin/
> > $ROOT/man/man1/
> > $ROOT/man/man3/
>
> Is this not just --install_base (M::B) or INSTALL_BASE (recent
> EU::MM)?
No, --install_base looks like this:
$ROOT/lib/perl5/$Config{archname}
$ROOT/lib/perl5
$ROOT/bin
$ROOT/man/man1
$ROOT/man/man3
Which means that you have architecture specific stuff in your lib/perl5
directory. So for a mac you might have something like:
$ROOT/lib/perl5/darwin-2level/Encode/Alias.pm
I don't know that someone could get Perl to try to load a package named
"package darwin-2level::Encode::Alias" since that's not a legal package
name, but I don't know that all architectures could have names which
aren't legal package names. I'd prefer them to be in separate
directories.
That being said, we've bit the bullet and rearranged our libraries to
fit '--install-base'. There's some short term pain there, but in the
long run, it seems like a win.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Perl and CGI - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog - http://use.perl.org/~Ovid/journal/
