From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)
Date: Sat, 16 Aug 2003 12:20:30 +0200 [thread overview]
Message-ID: <200308161220.31367.pauldv@gentoo.org> (raw)
In-Reply-To: <200308161146.16771.kaschu@t800.ping.de>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2099 bytes --]
On Saturday 16 August 2003 11:46, Karsten Schulz wrote:
> Hi all,
>
> At bugs.gentoo.org I attached an tarball with my version of an ebuild,
> which automatically will install *only* those security updates, which are
> relevant to your system (see
> <http://bugs.gentoo.org/show_bug.cgi?id=5835>).
>
> The trick is the following code in the ebuild:
> DEPEND="
> $(has_version 'nfs-utils' && echo '>=nfs-utils-1.0.4')
> $(has_version 'gnupg' && echo '>=gnupg-1.2.2-r1')
> "
> this will create dependencies on the fly: Only if you have nfs-utils
> installed, the new version with the bugfix will appear as a dependency.
> Same with gnupg.
> There is no need for new 'emerge' options or KEYWORDS.
>
> For his own system, the admin has to type in only:
> emerge rsync
> emerge security
>
> or, if he is interested in this stuff:
> emerge rsync
> emerge -p security
> and followed by 'emerge security', if necessary.
>
> The only drawback at the moment is, that there is no automated way to
> generate the value of the DEPEND variable by the GLSAs. Maybe here can
> Marius' XML format help. With GLSAs in such a format, a simple script can
> generate the security-ebuilds, the postings at forums.gentoo.org and the
> mails in gentoo-announce! I would love to hear from some core developers
> and others what you think (is it critical to use an ebuild, which does not
> compile and install its own sourcecode, because it has none?).
>
> I know, that this can (and must) be improved in the future (more
> information, references to advisories, signing the ebuild, a.s.o.), but at
> the moment, this way seems to me to be an easy one, isn't it?
>
> Comments?
Unfortunately dynamic dependencies in this style are not possible. I also
believe that a more fundamental solution should be implemented. Probably in
emerge itself. It should not really be hard. It should basically do what you
propose from a dynamically generated list of insecure ebuilds.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-16 10:20 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 [this message]
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
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=200308161220.31367.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/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