Re: Updating scanners and filters in Debian stable (3.1)

[paddy <paddy@panici.net>]

On Mon, Sep 13, 2004 at 12:45:34PM -0400, Stephen Gran wrote:
> This one time, at band camp, Martin Schulze said:
> > A while ago there was a discussion in which it was said that such
> > tools are rather useless (or even dangerous) if they don't get their
> > database updated in accordance with new viruses/security problems.
> > 
> > Some of these systems are hence not suitable for a stable Debian
> > release where updates will only be made for security problems and
> > very important bugfixes.
> > 
> > Have you thought about keeping these packages out of sarge or did you
> > develop a solution so that users can get their databases updated
> > outside of the stable Debian release?
> 
> ClamAV uses freshclam for virus definitions, so the actual database
> updates are covered.  That being said, there are relatively frequent
> changes to the scanning engine as well, leaving me feeling like it may
> not be the best choice for a stable release.  I do plan to continue
> offering out of band up dates on p.d.o, but I am not sure this is the
> best way to proceed.  Feedback welcome,

Stephen,

Revisiting your original question.

Reading the Debian Policy Manual as I am right now:

	2.2.1 The main section
	...
	packages in main ...
	must not be so buggy that we refuse to support them

While you clearly do not refuse, it was argued that the net effect is 
likely to be just so.

Perhaps the question now should be:  does volatile modify this?

(for example, does volatile count as support for this purpose).

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall