From: Stefan Monnier <monnier@iro.umontreal.ca>
To: <tomas@tuxteam.de>
Cc: emacs-devel@gnu.org
Subject: Re: Fwd: Should package.el support notifying on package security updates?
Date: Sat, 13 Aug 2022 10:00:40 -0400 [thread overview]
Message-ID: <jwv4jygs17n.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <YvcveXullXqScmj3@tuxteam.de> (tomas@tuxteam.de's message of "Sat, 13 Aug 2022 06:58:33 +0200")
> So the advocates of having this kind of flagging should be
> the ones responsible for digging up new resources, IMO.
In the context of ELPA, I could suggest the following path:
- Step 1: improve the protocol so that `package.el` can display the
"recent news" that (Non)GNU ELPA archives show in the HTML page (and
the release announcements emails).
- Step 2: highlight keywords like "security fix" in the "recent news".
- Step 3: improve the "recent news" system so that `package.el` could
distinguish the part of the news corresponding to the potential update
(currently the recent news is not parsed so we don't know which news
applies to which version).
- Step 4: highlight the updates that include "security fix" in their news.
I'm not sure "step 4" would be useful in the current context, but maybe
by the time we have made the previous steps (which are useful regardless
of step 4) the situation will be different.
Stefan
next prev parent reply other threads:[~2022-08-13 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r12qm4q5.fsf@gmail.com>
2022-08-08 1:46 ` Fwd: Should package.el support notifying on package security updates? Gulshan Singh
2022-08-12 0:04 ` Matt Armstrong
2022-08-12 0:29 ` Tim Cross
2022-08-12 13:18 ` Stefan Kangas
2022-08-13 0:44 ` Tim Cross
2022-08-12 21:40 ` Stefan Monnier
2022-08-13 0:58 ` Tim Cross
2022-08-13 4:58 ` tomas
2022-08-13 14:00 ` Stefan Monnier [this message]
2022-08-14 3:23 ` Richard Stallman
2022-08-14 3:29 ` Gulshan Singh
2022-08-16 2:52 ` Richard Stallman
2022-08-25 3:32 ` Richard Stallman
2022-08-25 4:33 ` Tim Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4jygs17n.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).