On Wed, Jan 16, 2008 at 10:09:15AM +0100, Florian Weimer wrote:
> Yes, this should be possible. I will think a bit abot it end try to
> write some code to implement this. It will be easier if we also include
> resolved security issues in the count (otherwise, it's hard to express
> the state in a single number).
Well, to PTS end it is enough to have a file containing the needed
information to decide whether or not the link should be put. If to you
it's easy to generate a list of vulnerabilities affecting the various
packages, with information whether they are resolved or not that's fine
for the PTS. In addition, given that you are asking for adding the
link, you're probably the most titled guys to know which kind of
information are needed to decide whether or not to add the link :-)
> > The PTS usually only provides some link when there's something
> > intesresting to watch behind the link.
> The drawback is that the link only appears after the next PTS update.
> (We could AJAX to create the link. 8-P)
Patches welcome :-P but anyhow that is totally unrelated with the point
above, even with AJAX you would need to decide whether or not to add the
link. You can only gain that you can do a query on a per-package
resource to check whether it should be added (besides of course being
more up to date, but that was not the topic of discussion here).
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org} -<%>- http://upsilon.cc/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
Attachment:
signature.asc
Description: Digital signature