[TriLUG] CPAN and SpamAssassin

Jeremy Portzer jeremyp at pobox.com
Fri Jul 30 11:35:26 EDT 2004


The problem here is that you are mixing two different package management
systems.  This is a recipe for disaster unless you are really careful.
CPAN's shell ("perl -MCPAN -e shell") uses its own system for
installing, compiling, and keeping track of modules.  This doesn't
interface with RPM at all, so RPM has no idea that you've installed the
HTML::Parser this way.

Fortunately, there's a very nice solution.  Instead of the CPAN shell
commands, use the "cpan2rpm" script (google-it) to automatically
download, compile, and RPM-ize Perl modules.  "cpan2rpm -i HTML::Parser"
would be all you'd need to type.  If building as non-root, which you
should for safety, it will automatically run sudo for the RPM
installation step.

And why in the world are you using RHL 7.1?  Upgrade to Fedora Core 2,
or RHEL or CentOS 3. :-)

Jeremy

On Fri, 2004-07-30 at 11:22, gregbrown at mindspring.com wrote:
> Okay.  I'm trying to install SpamAssassin a RH 7.1 machine.  So far 
> I've got the machine upgraded via yum about as far as it can be.
> 
> When I try to install perl-Mail-SpamAssassin-2.63 I get the following 
> error:
> 
> perl(HTML::Parser) is needed 
> 
> So I go to CPAN (perl -MCPAN -e shell).  I did a full update of CPAN 
> from the sell, reloaded CPAN then tried the following:
> 
> cpan> install HTML::Parser
> 
> to which I got:
> 
> HTML::Parser is up to date.
> 
> Okay...
> 
> So, CPAN says I have HTML::Parser and RPM doesn't.  Any ideas on 
> how I can resolve this?
> 
> Greg
-- 
/---------------------------------------------------------------------\
| Jeremy Portzer        jeremyp at pobox.com      trilug.org/~jeremy     |
| GPG Fingerprint: 712D 77C7 AB2D 2130 989F  E135 6F9F F7BC CC1A 7B92 |
\---------------------------------------------------------------------/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20040730/d20d5a26/attachment.pgp>


More information about the TriLUG mailing list