From: "Benedikt Morbach" <benedikt.morbach@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dedicated USE-flag is inconsequent and confusing
Date: Thu, 15 May 2008 15:42:56 +0200 [thread overview]
Message-ID: <6faa67950805150642l502cf46apfad307fbd0b9fd0f@mail.gmail.com> (raw)
In-Reply-To: <482C13EE.4050309@gentoo.org>
I think it should be made consistent or it should be turned into a
local use flag.
no-* or *-only flag don't make sense in my opinion, because you can
get the same with:
-gui instead of nogui (maybe -gtk/-qt4/-kde or something would be even better)
-* server instead of server-only (sure, this can only be done for each
single package, but it looks cleaner to me than -only)
Benedikt
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-05-15 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 11:58 [gentoo-dev] dedicated USE-flag is inconsequent and confusing Albert Zeyer
2008-05-15 10:43 ` Marijn Schouten (hkBst)
2008-05-15 13:42 ` Benedikt Morbach [this message]
2008-05-15 14:24 ` Albert Zeyer
2008-05-16 1:07 ` [gentoo-dev] " Duncan
2008-05-16 16:05 ` Santiago M. Mola
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=6faa67950805150642l502cf46apfad307fbd0b9fd0f@mail.gmail.com \
--to=benedikt.morbach@googlemail.com \
--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