Dag Wieers wrote on Wed, 17 Nov 2010 13:23:52 +0100 (CET): > Looking at the SPEC file, I see the ClamAV project still shipping (and > installing) the .cvd files. So somehow I wonder what the purposes of this > is.
Me, too :-) From what I gather the .cvd files are compressed versions of the cld files. Apparently clamav unpacks them in memory before using. So, for clamd using .cld is probably almost no advantage other than the startup of the daemon is a bit faster, but for clamscan it might be quite noticable. When you have both versions of say main.* in the clamav directory the daemon will complain on startup and ask you to remove one of them. However, it doesn't tell which is the preferred one. When these files were first introduced (with 0.96 I think) I removed all my .cvd files going by the fact that the .cld files had a newer timestamp and ran freshclam which fetched all the .cld versions. So I deduced that .cld is the preferred format. > Do you know how a packager is supposed to do this ? I have no idea, I'm not a packager ;-) Possible solutions: - provide a package with that dependency and one without it - if install is an update then don't have that dependency (don't know if that is possible) - similar: if install finds a /var/clamav/main.cld file not older than 30 days don't have that dependency (again, I don't know if that is possible) > > PS On the internal clamav packaging list there have been discussions > regarding not including the virus database as part of the tarball. I think that makes sense. definitions grow old very soon and you have to update regularly. Maybe on a system with no net access it's better to have an old database than none, though. But I > still prefer to have a clamav-db package for offline installation/usage. then maybe just remove the dependency and place a readme about the available database package in a good place? Or read that out to console when a fresh install happens? Kai -- Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
