This is a multi-part message in MIME format.
--------------080709080302010908090201
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
First of all, I appreciate the work.
I prefer to install the empty db package, and have freshclam download
the initial database. I didn't see a db-empty package in your spec
file. I had some issues where after updating clamav, freshclam named
the updated db files differently than came in the db package, and I
ended up with clam complaining about having two databases.
My take from
https://bugzilla.redhat.com/show_bug.cgi?id=573191 was to
add --disable-llvm to the build for EL5, since AFAIK the EL5 SELinux
package doesn't have the clamd_use_jit boolean (I haven't checked 5.6).
Fred
On 2/14/2011 5:18 PM, Kevin Fenzi wrote:
Greetings.
Last week at the epel meeting we talked about clamav and getting it
updated and maintained better. One of the issues that came up is that
folks would prefer a more understandable spec. That would help maintain
and keep it updated better.
Toward that end I have:
http://www.scrye.com/~kevin/fedora/clamav/
This is a package based on Dag's package from a while back and updated
for Fedora guidelines, etc.
In some simple testing on epel5 and epel6 it works pretty well. It
upgrades the existing packages ok, with one exception: You need to
'mv /etc/freshclam.conf.rpmnew /etc/freshclam.conf' in order to get
freshclam happy. I'm not sure of a way around this, but if anyone has
one, I'd love to hear it.
I mailed the EPEL maintainers of clamav last week and got one reply
saying the spec seemed fine, but nothing back from the other
co-maintainers. I'd like to set a time (say a week from now?) where we
just commit this new spec and push out updates for testing.
Thoughts? Comments? Flames?
kevin
_______________________________________________
epel-devel-list mailing list
epel-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
--------------080709080302010908090201
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
First of all, I appreciate the work.<br>
<br>
I prefer to install the empty db package, and have freshclam
download the initial database. I didn't see a db-empty package in
your spec file. I had some issues where after updating clamav,
freshclam named the updated db files differently than came in the db
package, and I ended up with clam complaining about having two
databases.<br>
<br>
My take from <a class="moz-txt-link-freetext"
href="https://bugzilla.redhat.com/show_bug.cgi?id=573191">ht...
was
to add --disable-llvm to the build for EL5, since AFAIK the EL5
SELinux package doesn't have the clamd_use_jit boolean (I haven't
checked 5.6).<br>
<br>
Fred<br>
<br>
On 2/14/2011 5:18 PM, Kevin Fenzi wrote:
<blockquote cite="mid:20110214151839.0306c537@ohm.scrye.com"
type="cite">
<pre wrap="">Greetings.
Last week at the epel meeting we talked about clamav and getting it
updated and maintained better. One of the issues that came up is that
folks would prefer a more understandable spec. That would help maintain
and keep it updated better.
Toward that end I have:
<a class="moz-txt-link-freetext"
href="http://www.scrye.com/~kevin/fedora/clamav/">http://www...
This is a package based on Dag's package from a while back and updated
for Fedora guidelines, etc.
In some simple testing on epel5 and epel6 it works pretty well. It
upgrades the existing packages ok, with one exception: You need to
'mv /etc/freshclam.conf.rpmnew /etc/freshclam.conf' in order to get
freshclam happy. I'm not sure of a way around this, but if anyone has
one, I'd love to hear it.
I mailed the EPEL maintainers of clamav last week and got one reply
saying the spec seemed fine, but nothing back from the other
co-maintainers. I'd like to set a time (say a week from now?) where we
just commit this new spec and push out updates for testing.
Thoughts? Comments? Flames?
kevin
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
epel-devel-list mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:epel-devel-list@redhat.com">epel-devel-list@redhat.com</a>
<a class="moz-txt-link-freetext"
href="https://www.redhat.com/mailman/listinfo/epel-devel-list"&...
</pre>
</blockquote>
<br>
</body>
</html>
--------------080709080302010908090201--