On 8/2/07, Tom Phoenix <[EMAIL PROTECTED]> wrote:
> On 8/2/07, Larry Vaden <[EMAIL PROTECTED]> wrote:
>
> > What controls whether a Perl module is chosen from
>
> The order of directories in @INC controls this; the first module found
> is the one that's used. Does that give you what you need?
>
> Cheers!
>
> --Tom Phoenix
> Stonehenge Perl Training
Thanks, Tom!
The output of grep -i "@inc" /usr/bin/spamassassin is:
unshift ( @INC, '../blib/lib' );
{ unshift ( @INC, $dir ); last; }
-pathlist => [EMAIL PROTECTED],
pod2usage( -verbose => $verbose, -message => $message, -exitval =>
64, -input => "spamassassin-run.pod", -pathlist => [EMAIL PROTECTED] );
which is over my head :)
Is it true that
use lib '/usr/lib/perl5/vendor_perl/5.8.5'; in /usr/bin/spamassassin
would cause .pm modules in /vendor_perl/ to be chosen over those in
/site_perl/?
Is it true that
perl -MCPAN -e 'install A::B' updates /site_perl/ rather than /vendor_perl/?
The reason I ask is that /vendor_perl/ has Net::DNS version 0.48 and
/site_perl/ has Net::DNS version 0.61 and if I understand the Net::DNS
release notes, one wants an SPF-specific fix just released in Net::DNS
version 0.61.
IOW, how does one go about benefiting from using perl -MCPAN to update
Perl modules?
kind regards/ldv
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
