From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New global USE flag: modplug
Date: Fri, 02 Nov 2007 15:15:10 +0100 [thread overview]
Message-ID: <472B30EE.9040105@gentoo.org> (raw)
In-Reply-To: <20071102140115.32330f85@epia.jer-c2.orkz.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeroen Roovers wrote:
> On Fri, 02 Nov 2007 13:40:40 +0100
> "Marijn Schouten (hkBst)" <hkBst@gentoo.org> wrote:
>
>> Another prime example for use flags with more than two values:
>>
>> mod=off
>> mod=fmod
>> mod=libmodplug
>>
>> the first for disabling mod support, the second for enabling it and
>> preferring fmod implementation, the third for enabling it and
>> preferring libmodplug implementation.
>
> I don't think you've actually argued the case why one USE flag with
> three, perhaps four modes (off, fmod, libmodplug, and perhaps default)
> is preferable to two USE flags with two modes each (fmod and modplug,
> both refering to the libs a package links to, either on or off).
I tried to explain this before. See
<http://article.gmane.org/gmane.linux.gentoo.devel/52316/match=use+options>.
Having an ordinary use flag for each library may work well enough when there
are less than three libraries that provide a certain functionality, although
with 2 old-style use flags you already have one bogus fourth option. Default
should not be an option of its own; one of the three options should be the
default.
> Besides, could you explain why are you trying to hijack a short and
> simple thread about globalising one or two USE flags?
I'm not trying to hijack this thread. I'm just injecting one message pointing
this out as something I think could benefit from my proposal.
A few real examples may go a long way to explaining something.
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
iD8DBQFHKzDup/VmCx0OL2wRAo5vAJ0VLX8BSFLFTY2K1wLADtS35jZHnwCfS8Vd
IgDXBRNrzWbiLfuZadHIzj8=
=MHt+
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-02 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 21:32 [gentoo-dev] New global USE flag: modplug Samuli Suominen
2007-11-01 23:18 ` Drake Wyrm
2007-11-02 12:08 ` [gentoo-dev] " Duncan
2007-11-02 5:11 ` [gentoo-dev] " Josh Saddler
2007-11-02 12:28 ` Jeroen Roovers
2007-11-02 12:40 ` Marijn Schouten (hkBst)
2007-11-02 13:01 ` Jeroen Roovers
2007-11-02 14:15 ` Marijn Schouten (hkBst) [this message]
2007-11-02 12:42 ` Marijn Schouten (hkBst)
2007-11-02 13:59 ` Samuli Suominen
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=472B30EE.9040105@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