From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: use flags -> use options
Date: Mon, 08 Oct 2007 16:48:53 +0200 [thread overview]
Message-ID: <470A4355.7090709@gentoo.org> (raw)
In-Reply-To: <fedfg2$ant$1@sea.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ryan Hill wrote:
> 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?
No, if what I'm saying makes no sense it is ignorance. Please enlighten me.
Marijn
- --
Marijn Schouten (hkBst), Gentoo Lisp project
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHCkNVp/VmCx0OL2wRAv1/AJ9GBpu8wL6NL4Xw8sawwPEeHAmkdQCeJFqF
fq8NiFnqnV9NBErojijBW+A=
=LO9y
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-08 15:00 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
2007-10-08 14:48 ` Marijn Schouten (hkBst) [this message]
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=470A4355.7090709@gentoo.org \
--to=hkbst@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