[oe] [PATCH] clamav: allow clamav-data installation

[Khem Raj]

On Sat, Aug 21, 2010 at 11:19 AM, Roman I Khimov <roman at khimov.ru> wrote:
> В сообщении от Суббота 21 августа 2010 21:38:48 автор Khem Raj написал:
>> On Sat, Aug 21, 2010 at 9:03 AM, Roman I Khimov <khimov at altell.ru> wrote:
>> > It wasn't possible to install prepackaged clamav-data with the way it's
>> > been packaged. And there are situations where you want to have at least
>> > prepackaged AV databases before you could do any sort of update. Also,
>> > logically freshclam doesn't substitute clamav-data, but rather
>> > complements it.
>> >
>> > Signed-off-by: Roman I Khimov <khimov at altell.ru>
>>
>> Will there be any conflicts with prepackaged clamav-data
>> otherwise you have the ack.
>
> Well, -data is data. -freshclam is freshclam. Freshclam updates the data, but
> the data files are defined as CONFFILES already, so there is no conflict at
> this level.
>
> But thinking another 5 minutes about it there is an issue with this patch in
> that it actually makes clamav-data installation (and that is huge, 25M)
> _mandatory_, whether you want that or not depends on situation. We want that
> (hence the patch), someone might not.
>
> Technically, there are three possible installation combinations, each has its
> valid use:
>  * clamav-data
>  * clamav-freshclam
>  * clamav-data & clamav-freshclam
>
> Before the patch only second one was possible (probably with the recent
> BAD_RECOMMENDATIONS fixes to opkg and OE also the first one). After the patch
> only first and third will be possible. Do we really care about second case?

Can clamav-freshclam function without clamav-data? If yes then
I guess if someone does not need it and does not need data
and is forced to install would be unwelcome particularly when
the size is big enough.

> And if yes, how to allow all of three to coexist?
>

may be have separate recipe for data.

> --
>  http://roman.khimov.ru
> mailto: roman at khimov.ru
> gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>