On Dec 21, 2007 4:25 PM, Ovid <[EMAIL PROTECTED]> wrote:
> 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.
I think that if you 'use lib qq{$ROOT/lib/perl5}' then the
architecture directory gets added automatically. (According to
'perldoc lib').
Maybe I just don't understand what you're trying to do well enough to
see why architecture specific directories are a problem. (XY
problem?)
David
