From: Karsten Schulz <kaschu@t800.ping.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)
Date: Sat, 16 Aug 2003 13:03:28 +0200 [thread overview]
Message-ID: <200308161303.28172.kaschu@t800.ping.de> (raw)
In-Reply-To: <200308161220.31367.pauldv@gentoo.org>
Am Samstag, 16. August 2003 12:20 Paul de Vrieze wrote:
> Unfortunately dynamic dependencies in this style are not possible.
Why not? Please, could you explain me what will break?
(or show me the lines in ebuild.sh were things will break?)
On my machine the generation of the dependencies work (Portage 2.0.48-r5
(default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)).
I tried it with my security-1.0.ebuild.
I did some quick tests with several package combinations and the only thing I
noticed was, that the compile and install stages cause some heavy cpu cycles,
which I can not explain. (maybe the empty SRC_URI var, but why?)
> I also
> believe that a more fundamental solution should be implemented. Probably in
> emerge itself.
I agree on that for future developments. But when will that be implemented? I
tried a simple solution for now. I really like to see an 'security' argument
like 'system' or 'world' in Portage 2.x.
OTOH I wish to keep server administration simpler now, because easier security
administration is nothing, which must wait for tomorrow (imho).
>It should not really be hard. It should basically do what
> you propose from a dynamically generated list of insecure ebuilds.
ACK.
Karsten
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-16 11:03 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 [this message]
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=200308161303.28172.kaschu@t800.ping.de \
--to=kaschu@t800.ping.de \
--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