public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: use flags -> use options
Date: Tue, 09 Oct 2007 12:20:30 +0200	[thread overview]
Message-ID: <470B55EE.1000909@gentoo.org> (raw)
In-Reply-To: <20071008214058.3d647e4e.genone@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marius Mauch wrote:
> So what you want is a USE_EXPAND version that only allows one value
> per variable. That wouldn't be terribly difficult to do.

I extremely dislike that characterization. What I want is use flags with more
than two possible values. I see no reason to warp that to fit USE_EXPAND.
There may even be uses where this could be used in combination with USE_EXPAND.

> As for your idea (ignoring implementation issues), I'd expect that
> sooner or later people will request multivalue functionality as well,
> so we'd have the same situation there.

Right, current use flags are "2 options, pick 1", I am requesting "n options,
pick 1" and you're saying "n options, pick m, (m<n)" might be useful too.

But "n options, pick m, (m<n)" reduces to n times "2 options, pick 1" (you
decide for each possible value whether to include it or not). This is exactly
why our "2 options, pick 1" system works so well most of the time.

> Also in the given example, how
> would the user/package manager actually know what values were
> valid/available for "impl"?

That is a good question. If all possible options need to be specified a syntax
should be developed for that. How about:

IUSE="+default_on_flag normalflag
multiwayflag={option1,option2,+default_option} -default_off_flag",

or

IUSE="+default_on_flag normalflag multiwayflag={option1 option2
+default_option} -default_off_flag",

or

IUSE="+default_on_flag normalflag multiwayflag=(option1 option2
+default_option) -default_off_flag".

In use.[local.]desc the multiwayflag description should explain what each
alternative means.

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

iD8DBQFHC1Xup/VmCx0OL2wRAnrfAJkBLMTuzlpu6g4uhZW6429hJ3gsUgCgr8h7
2cX5/qHGbj4Y3GgDCw/uSrk=
=pVPW
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2007-10-09 10:30 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)
2007-10-08 19:40         ` Marius Mauch
2007-10-09 10:20           ` Marijn Schouten (hkBst) [this message]

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=470B55EE.1000909@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