Ralph Angenendt wrote: > [EMAIL PROTECTED] wrote: > >> I have installed it just fine using the source from the ClamAV site. >> It works quite well. I use the OpenSSL version that comes default in >> ClamAV. My only ./configure switches that are used are: >> --disable-zlib-check and --enable-experimental. > > Yes, but that works around package management. Some people (including > me) don't want to do that. And rpmforge is pretty fast with updates to > ClamAV. >
It doesn't have to - one can build the product from source and then create the package. For consistency you would have to accurately recreate the existing package structure so that you don't end up with a mixed bag of concurrent versions. Or - remove all vestiges of existing packages and build to your design. It does give you some independence from vendors and their schedules/skills/process management standards for everything, but it requires you to have and maintain a proper build environment and depot for creating, packaging, and retaining versions of interest. Unless you're in a heavily configuration-managed environment this is not the likely solution for a lot of sites. It is for me, as it happens. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
