From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] virtualx eclass
Date: Fri, 17 Oct 2008 01:18:14 +0200 [thread overview]
Message-ID: <200810170118.21379.bo.andresen@zlin.dk> (raw)
In-Reply-To: <20081016215432.GA15437@comet>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On Thursday 16 October 2008 23:54:32 Donnie Berkholz wrote:
> I'm not sure whether this would work, but one idea would be to handle
> dependencies depending on what's in IUSE of the ebuild inheriting.
That would require ebuilds to set IUSE before inheriting the eclass.
--
Bo Andresen
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-16 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 13:44 [gentoo-dev] virtualx eclass Doug Goldstein
2008-10-16 14:17 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-10-16 14:32 ` Doug Goldstein
2008-10-16 15:15 ` Doug Goldstein
2008-10-16 14:18 ` [gentoo-dev] " Doug Goldstein
2008-10-16 15:35 ` Doug Goldstein
2008-10-16 21:54 ` Donnie Berkholz
2008-10-16 23:18 ` Bo Ørsted Andresen [this message]
2008-10-20 21:50 ` Doug Goldstein
2008-10-22 11:06 ` Petteri Räty
2008-10-28 17:32 ` Doug Goldstein
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=200810170118.21379.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-dev@lists.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