[csw-pkgsubmissions] newpkgs clamav, libclam6, libclam6_devel

Philip Brown phil at bolthole.com
Wed Dec 15 18:17:39 CET 2010

On Wed, Dec 15, 2010 at 12:07 AM, Peter Bonivart <bonivart at opencsw.org> wrote:
> On Wed, Dec 15, 2010 at 1:43 AM, Ben Walton <bwalton at opencsw.org> wrote:
>> Excerpts from Philip Brown's message of Tue Dec 14 18:05:45 -0500 2010:
>>> But, is it really a good idea to ship anything in /var/opt?  Our
>>> normal standards say "no".
>>> Could you describe more about what is going on here please?
> We had this discussion two years ago, whether to provide signature
> databases or not with the package. Most thought it was of use,
> especially for the new user who may not even know about freshclam or
> have set up his infrastructure so freshclam can actually fetch any
> updates from the mirrors.

and I think that this is a good idea. Thanks for the refresher on that info
(might be nice to put it in the "i cswreleasemgr" file)
But if you read the specific question I had, it was not "should we
ship a signature database", but "should we ship it in /var/opt?"

This is not a "random new rule": it was generally agreed upon, a while
back, that shipping files in /var was usually a bad idea, and that it
was preferable to generate them from templates in /opt/csw at install

So how about moving

to /opt/csw/share/clamav/ or something, and then implementing a
"if {var file} does not exist, copy in this file instead" postinstall ?

More information about the pkgsubmissions mailing list