Re: Updating scanners and filters in Debian stable (3.1)
Jesus Climent <firstname.lastname@example.org> writes:
> Except that those private repositories and backports have no policy
> and no maintenance. My proposal is to create a policy for a
> repository with maintenance, security updates which introduces new
> packages and provides new functionality on outdated or useless
> packages from stable, and is built against stable.
So all of that could be done on backports but the very first. WHY do
we want "security updates which ... provide new functionality"?
What about that is a "security update"?
Suppose a nifty new emacs feature is developed; why should that new
functionality be excluded from this repository you are speaking of,
merely because it isn't a security update?
In other words, it sounds like the whole virus-scanner bit is a red
herring, and what you actually want is just a repository that doesn't
have the stability restrictions that Debian normally has. Maybe
that's a good idea, but it needs to be argued for by something other
than "oooh, virus scanners!"