From: Karsten Schulz <kaschu@t800.ping.de>
To: Klavs Klavsen <kl@vsen.dk>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)
Date: Sat, 16 Aug 2003 18:18:57 +0200 [thread overview]
Message-ID: <200308161818.57956.kaschu@t800.ping.de> (raw)
In-Reply-To: <1061049373.3338.4.camel@amd.vsen.dk>
Am Samstag, 16. August 2003 17:56 Klavs Klavsen wrote:
> How about starting with putting the GLSA's in the tree?
> That would be step 1.
ack. Let us talk about the format! For future enhancements I suggest using an
xml format (Marius?).
> After this, I agree it would be best to add a --security option.
>
> IMHO this should work, so emerge -u world --security (or -S - or is that
> too close to -s?) would look at all the upgrades suggested by the world
> - and then check against the glsa's and see if any of them have are
> mentioned here. The glsa's should be named after the package version
> that fixes this issue, that way it would be easy to check and upgrade if
> the currently installed is older.
after I learned from Paul, that I cannot use dynamically generated
dependencies, I would second this suggestion.
Karsten
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-16 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 9:46 [gentoo-dev] RFC: security updates only? (security-1.0.ebuild) Karsten Schulz
2003-08-16 10:20 ` Paul de Vrieze
2003-08-16 11:03 ` Karsten Schulz
2003-08-16 11:19 ` Karsten Schulz
2003-08-16 14:31 ` Paul de Vrieze
2003-08-16 15:56 ` Klavs Klavsen
2003-08-16 16:18 ` Karsten Schulz [this message]
2003-08-16 15:59 ` Karsten Schulz
2003-08-16 17:11 ` Paul de Vrieze
2003-08-16 19:38 ` Marius Mauch
2003-08-18 10:29 ` Karsten Schulz
2003-08-18 19:17 ` Marius Mauch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308161818.57956.kaschu@t800.ping.de \
--to=kaschu@t800.ping.de \
--cc=gentoo-dev@gentoo.org \
--cc=kl@vsen.dk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox