From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: use flags -> use options
Date: Mon, 08 Oct 2007 08:40:02 -0600 [thread overview]
Message-ID: <fedfg2$ant$1@sea.gmane.org> (raw)
In-Reply-To: <470A1840.10505@gentoo.org>
Marijn Schouten (hkBst) wrote:
> Marius Mauch wrote:
>> We already have this with USE_EXPAND. Not exactly the same syntax, but
>> I don't see a terrible problem in that, and we don't have to fix all
>> three trillion related tools to handle it. Unless you can come up
>> with a case that can't be handled with USE_EXPAND.
> No, USE_EXPAND is only a way to abbreviate use flags with a common substring
> in their name, such as "impl_guile impl_sbcl impl_clisp" which could be
> encoded interchangeably as either
You're kidding, right?
> USE EXPAND Defines a list of variables which are to be treated incrementally and who
> contents are to be expanded into the USE variable as passed to ebuilds. Expansion
> done as per Algorithm 2. So, for example, if USE EXPAND contains ‘ALSA CARDS’, an
> the ALSA CARDS variable contains ‘foo’, ‘alsa_cards_foo’ will be appended to USE.
> Algorithm 2: USE EXPAND logic
> for each variable V listed in USE EXPAND do
> for each token T in V do
> append v_T to USE, where v is the lowercase of V
> end for
> end for
--
fonts / wxWindows / gcc-porting / treecleaners
EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 (0xF9A40662)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-08 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47090820.7060506@gentoo.org>
2007-10-07 18:09 ` [gentoo-dev] Re: use flags -> use options Christian Faulhammer
2007-10-07 19:12 ` Tobias Klausmann
2007-10-07 22:00 ` Jan Kundrát
2007-10-08 4:17 ` Drake Wyrm
2007-10-08 2:43 ` Marius Mauch
2007-10-08 11:45 ` Marijn Schouten (hkBst)
2007-10-08 14:40 ` Ryan Hill [this message]
2007-10-08 14:48 ` Marijn Schouten (hkBst)
2007-10-08 19:40 ` Marius Mauch
2007-10-09 10:20 ` Marijn Schouten (hkBst)
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='fedfg2$ant$1@sea.gmane.org' \
--to=dirtyepic@gentoo.org \
--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