On Fri, Oct 27, 2000 at 09:11:59PM -0400, Michael P. Soulier wrote:
> On Wed, Oct 25, 2000 at 06:44:33PM +0200, Bernd Worsch wrote:
> >
> > Question A: Where are those paths defined?
> > ($PERLLIB and $PERL5LIB are not set!)
>
> In the source code, at compile time.
>
> Check out the "use lib" pragma. You can prefix the @INC list.
>
Well, maybe that will do.
> > Question B: May i run into problems when actually using the newer locals?
> > Would it be safe to set:
> > @INC = /usr/local/lib/site_perl/i386-linux
> > /usr/local/lib/site_perl
> > /usr/lib/perl5/5.005/i386-linux
> > /usr/lib/perl5/5.005
> > /usr/lib/perl5
> > .
>
> I wouldn't set the entire thing manually no. Use the lib pragma.
Yep, I thought people would say so! Let's be careful!
> > Question C: Could anybody tell me, why the Perl-Module-Tree seems to
> > be such a mess?
> > Where can i find out about it's inherent logic?
>
> Ask that question on comp.lang.perl.misc. I'm sure you'll get an earfull.
> ;-)
I'd think so, but the Question has kind of two different aspects to me:
First it is about understanding CPAN structure and how parts of it
get imported to my local computer using Perls' CPAN module for example.
(this is what comp.lang.perl.misc will teach me)
Second is about the debian way of doing things. Ok, Perl-Policy tells me
i'm allowed to install several Perl Versions at the same time.
That is fine and has consequences on directory structure, i see.
Perl-policy seems a bit out of date because the
directory-structure presented there does not match my local install.
But it works, which is great!
On the other hand the policy does not tackle the problem of how to
handle additional Perl modules not packaged for Debian.
Which is bad, because people need such packages.
(i hoped debian-user would teach me on this problem)
I even thought about finding out and proposing some patch to Debians'
perl-policy, but at the moment i lack the necessary understanding to
do so.
Maybe i'll nevertheless give it a try... (comments welcome)
Thanx
Bernd
--
--------------------------------------------------------
[EMAIL PROTECTED]
-------------------------------------email-preferred----
