[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Michael Banck wrote,

> ... If the data is limited to binary-all
> packages, ...

Exactly.  This is the infrastructure I would
have used, had it been available for sarge: the
binary-all data update.

> ... the amount of packages which are affected
> by this is quite narrow ...


If and when policy is written hereto, let the
policy writers please observe that---besides
virus scanners, spam filters and the like---one
further narrow class of packages want
post-release binary-all data updates.  These are
the few packages whose data depend on the
contents of the release itself.  They are no
security packages, but they do require more or
less similar post-release support.

Debram-data is a present example of the rare
type.  One or two other packages of this kind
might emerge from the Debtags project, were the
infrastructure available.

We Debtags developers admit that, in our
particular case, we seem to be doing well with
our existing data-update scheme.  Thus the
present post is no cry of distress; it is just a
quiet request.  The request is that the narrow
group of packages approved in principle for
post-release data-update support include the
rare packages of the kind described: packages
whose data depend on the contents of the release
itself.  If policy is written hereto, permission
in principle for such packages is sought.

For further understanding, see [1] and [2].

Thaddeus H. Black
508 Nellie's Cave Road
Blacksburg, Virginia 24060, USA
+1 540 961 0920, t@b-tk.org

1. http://debtags.alioth.debian.org
2. debram(1)

Attachment: pgp4O2sPEhsDU.pgp
Description: PGP signature

Reply to: