On Jun 15, 2012, at 7:39 AM, Matt Olney wrote:
> On Fri, Jun 15, 2012 at 9:46 AM, Brian Morrison <b...@fenrir.org.uk> wrote:
>
>> On Fri, 15 Jun 2012 09:13:30 -0400
>> Matt Olney <mol...@sourcefire.com> wrote:
>>
>>> We're having some trouble with our freshmeat account. You can
>>> download the latest here, until we get it fixed up:
>>>
>>> https://sourceforge.net/projects/clamav/files/
>>
>> The download is 14MB odd, previous version have been 48MB and when I
>> run my rpm build script it tells me that the main and daily cvd files
>> are missing.
>>
>> --
>>
>> Brian Morrison
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>> http://www.clamav.net/support/ml
>>
>
> Brian,
>
> It looks like our new build system doesn't bundle the .cvds. More
> accurately it ships 0-length main and daily cvds. For now you can, of
> course, run freshclam to pickup the signature files. We'll revisit the
> desired behavior (with or without cvds) and adjust our build process
> accordingly. Since you brought it up, do you have a preference or use-case
> that supports one behavior or the other?
>
> Matt
>
I'm not the OP but since you asked...
Short version...
It breaks my automated build script ;-)
Long version...
Ok so I can fix the script easily enough but I would prefer that .cvds remain
included with the source.
My build script fetches the source, verifies, does some checking around, and
then builds and publishes
a Solaris pkg5 package to our internal repo. I would prefer to work with one
tar ball over several.
This process creates an "out of the box" working package instead of requiring
user intervention.
Robert
--
Robert Hartzell
President | RwHartzell.Net, Inc.
www.rwhartzell.net | blogs.rwhartzell.net/bear
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
