Kris Deugau wrote:
(Please keep the discussion on-list.)
Sorry about that - just hit 'reply' without checking where the message
was actually going.
Edward Prendergast wrote:
Kris Deugau wrote:
Edward Prendergast wrote:
@@INSTALLSITELIB@@ /opt/perl5/lib/5.10.1/x86_64-linux
^^^^^^^^^^^^^^^^^^
This looks a little fishy...
I agree, I'm not sure where it's coming from.
FWIW, nothing like that showed up in my brief test - missing
substitutions like that are usually a sign of a build gone wrong from
early on.
That's a good question, but my qualms are mainly down wanting to
perhaps use local::lib and have up to date CPAN modules as it seems
to take a long time for these to filter down via redhat.
Mmm. I use the RPMForge repo for more up-to-date Perl modules, but
I've yet to run into any problems using the nominally outdated ones
filtering down from RedHat/CentOS. Net::DNS is the only module I can
think of where there are/were known issues (at least with respect to
SA's usage) in the stock version.
My motivations aren't purely SpamAssassin related - there are other
programs that want current Perl modules (MailScanner) and I wanted to
get SpamAssassin along side these.
This is based around what I've seen from local::lib:
http://search.cpan.org/~apeiron/local-lib-1.004009/lib/local/lib.pm#SYNOPSIS
Ah, hm. I think you should be fine just setting your path to call
your custom Perl ahead of the system Perl; that looks to be targetted
at cherrypicking module updates alongside the packaged system Perl.
Right you are! When I change my .bashrc to this:
#export MODULEBUILDRC="/opt/perl5/.modulebuildrc"
#export PERL_MM_OPT="INSTALL_BASE=/opt/perl5"
#export
PERL5LIB="/opt/perl5/lib/perl5:/opt/perl5/lib/perl5/x86_64-linux:/opt/perl5/lib/5.10.1:/opt/perl5/lib/site_perl/5.10.1"
export PATH="/opt/perl5/bin:$PATH"
SpamAssassin now installs OK.
> Essentially when I use perl from the command
line (and install other modules from CPAN) everything seems to be OK,
issues only appear to be arising with Mail::SpamAssassin.
Yeah, that's the weird bit. You might try installing SA from the
tarball instead of CPAN - I had some odd errors come up when I tried
via CPAN, but I have a feeling some of that had to do with doing the
whole test as non-root.
Still unsure where that @@INSTALLSITELIB@@ stuff was coming from but it
certainly looks like the issue is now resolved. Many thanks for all your
help.
-Edward
************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************
