[suggest] perl-Mail-ClamAV RPM

Dag Wieers dag at wieers.com
Wed May 2 14:20:44 CEST 2007


On Wed, 2 May 2007, Michael Mansour wrote:

> Hi Dag,
> 
> > On Wed, 2 May 2007, Michael Mansour wrote:
> > 
> > > I'm after a perl-Mail-ClamAV RPM. Would this be a good addition to rpmforge?
> > 
> > That's fine. I've been working on a perl SPEC file generator for 
> > RPMforge and it looks promising. I'll test it out on this one :)
> > 
> > Once the generator works reliably, we can start producing more perl 
> > RPM packages (or at least fill out the missing ones that break 
> > consistency).
> 
> That's good news.
> 
> So you know the way I did it today (I'd prefer repo's instead of doing this
> stuff myself, but I needed it as the new clamscan 0.90.2 uses way too much cpu
> loading the virus def files each time on each file it scans, much better to go
> with the perl module or clamd which loads the defs once and scans multiple
> files continuously thereafter).
> 
> The way I did it is:
> 
> 1. from Dag repo installed:
> 
> clamav-devel-0.90.2-1.el4.rf.i386.rpm
> perl-Inline-0.44-1.el4.rf.noarch.rpm
> perl-Parse-RecDescent-1.94-1.el4.rf.noarch.rpm
> 
> 2. verified install of bzip2-devel rpm from distribution. Both devel packages
> are needed otherwise can't compile perl module.
> 
> 3. downloaded Mail-ClamAV tarball from http://search.cpan.org/~sabeck/
> 
> 4. yum installed cpan2rpm from ATrpms repo.
> 
> 5. Created:
> 
> # echo "%_unpackaged_files_terminate_build 0" >> /etc/rpm/macros
> 
> or the cpan2rpm build will break with unpackaged files error from rpm.
> 
> 6. Ran:
> 
> # cpan2rpm Mail-ClamAV-0.20.tar.gz
> 
> which built RPM's in:
> 
> RPM: /usr/src/redhat/RPMS/noarch/perl-Mail-ClamAV-0.20-1.noarch.rpm
> SRPM: /usr/src/redhat/SRPMS/perl-Mail-ClamAV-0.20-1.src.rpm
> 
> 7. RPM contains:
> 
> ]# rpm -qilp /usr/src/redhat/RPMS/noarch/perl-Mail-ClamAV-0.20-1.noarch.rpm
> Name        : perl-Mail-ClamAV             Relocations: /usr
> Version     : 0.20                              Vendor: Scott Beck
> <sbeck at gossamer-threads.com>
> Release     : 1                             Build Date: Wed 02 May 2007
> 21:55:30 EST
> Install Date: (not installed)               Build Host: falcon.npgx.com.au
> Group       : Applications/CPAN             Source RPM:
> perl-Mail-ClamAV-0.20-1.src.rpm
> Size        : 78137                            License: Artistic
> Signature   : (none)
> Packager    : Arix International <cpan2rpm at arix.com>
> URL         : http://www.cpan.org
> Summary     : Mail-ClamAV - Perl extension for the clamav virus scanner
> Description :
> Clam AntiVirus is an anti-virus toolkit for UNIX
> L<http://www.clamav.com/>.  This module provide a simple interface to
> its C API.
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Mail
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Mail/ClamAV.pm
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/Mail
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/Mail/ClamAV
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/Mail/ClamAV/ClamAV.so
> /usr/share/doc/perl-Mail-ClamAV-0.20
> /usr/share/doc/perl-Mail-ClamAV-0.20/Changes
> /usr/share/doc/perl-Mail-ClamAV-0.20/INSTALL
> /usr/share/doc/perl-Mail-ClamAV-0.20/Inline
> /usr/share/doc/perl-Mail-ClamAV-0.20/Inline/MakeMaker.pm
> /usr/share/doc/perl-Mail-ClamAV-0.20/README
> /usr/share/man/man3/Mail::ClamAV.3pm.gz
> 
> 8. Installed RPM:
> 
> ]# rpm -Uvh /usr/src/redhat/RPMS/noarch/perl-Mail-ClamAV-0.20-1.noarch.rpm
> Preparing...                ########################################### [100%]
>    1:perl-Mail-ClamAV       ########################################### [100%]
> 
> Now using/testing it on one production server.
> 
> If you haven't used cpan2rpm before it's an excellent piece of software.

The problem with cpan2rpm and cpanflute2 is that they create a SPEC file 
that may work for on distribution, but not for all distributions we carry.

Also in this case, it is a binary RPM, not a noarch RPM. I have seen the 
same mistake being made by cpanflute. One of the remaining problems I 
have is to detect in advance whether it is a noarch build or an arch 
build.


> I'd prefer of course if a repo would carry this release, as it saves time and
> much more widely used and tested by others instead of building things myself.
> 
> Please do announce it here when you do have it in the forge.

The next update. I have them on my build system, but I do not push for a 
single package, too much overhead :(

Kind regards,
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]



More information about the users mailing list