On Sat, 29 Dec 2007 12:04:16 -0700, Kevin Fenzi wrote:
So, let me recap what I know and perhaps someone will think of a
brilliant solution:
- The fedora clamav maintainer wants to do things the way the package
is currently setup. They don't want to change it to be more simple/easy
to understand, or fix it to be more usable. This package meets all the
package guidelines.
- I attempted to setup a clamav for epel that was based on the dag
rpms. However, amavisd-new, klamav, and other packages in fedora (and
thus epel) depend on clamav being packaged in the way that it is. This
would mean all those other packages would have to rework their specs
for the clamav package.
- The amavisd-new maintainer in fedora/epel reluctantly agreed to
maintain the fedora version in EPEL.
So, I don't see much way out... we go with the version currently in
fedora/epel, unless someone can talk the maintainer (and the
maintainers of all the dependent packages) into changing the package.
Any other ideas?
What exactly would make the current packages "more usable"?
Why can't a volunteer create and maintain a clamav configuration add-on
package, which offers a single system-wide clamav daemon if that is
requested by the clamav user base in Fedora/EPEL?