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 16:31:28 +0200 [thread overview]
Message-ID: <200308161631.47162.pauldv@gentoo.org> (raw)
In-Reply-To: <200308161303.28172.kaschu@t800.ping.de>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 902 bytes --]
On Saturday 16 August 2003 13:03, Karsten Schulz wrote:
> 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?)
Well, for a user it works, but it does not work in terms of providing a cache.
Normally a cache is built. One thing needed for that is that we can parse
dependencies. Your dependencies are created in a bash way. That means that a
cache can not be created because as far as the caching system is concerned
your cache is dynamic. And worse, there would be no way of detecting this
dynamic nature. In short putting such an ebuild in the portage tree would
create hell.
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 14:31 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 [this message]
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=200308161631.47162.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