| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> So what you want is a USE_EXPAND version that only allows one value |
| 6 |
> per variable. That wouldn't be terribly difficult to do. |
| 7 |
|
| 8 |
I extremely dislike that characterization. What I want is use flags with more |
| 9 |
than two possible values. I see no reason to warp that to fit USE_EXPAND. |
| 10 |
There may even be uses where this could be used in combination with USE_EXPAND. |
| 11 |
|
| 12 |
> As for your idea (ignoring implementation issues), I'd expect that |
| 13 |
> sooner or later people will request multivalue functionality as well, |
| 14 |
> so we'd have the same situation there. |
| 15 |
|
| 16 |
Right, current use flags are "2 options, pick 1", I am requesting "n options, |
| 17 |
pick 1" and you're saying "n options, pick m, (m<n)" might be useful too. |
| 18 |
|
| 19 |
But "n options, pick m, (m<n)" reduces to n times "2 options, pick 1" (you |
| 20 |
decide for each possible value whether to include it or not). This is exactly |
| 21 |
why our "2 options, pick 1" system works so well most of the time. |
| 22 |
|
| 23 |
> Also in the given example, how |
| 24 |
> would the user/package manager actually know what values were |
| 25 |
> valid/available for "impl"? |
| 26 |
|
| 27 |
That is a good question. If all possible options need to be specified a syntax |
| 28 |
should be developed for that. How about: |
| 29 |
|
| 30 |
IUSE="+default_on_flag normalflag |
| 31 |
multiwayflag={option1,option2,+default_option} -default_off_flag", |
| 32 |
|
| 33 |
or |
| 34 |
|
| 35 |
IUSE="+default_on_flag normalflag multiwayflag={option1 option2 |
| 36 |
+default_option} -default_off_flag", |
| 37 |
|
| 38 |
or |
| 39 |
|
| 40 |
IUSE="+default_on_flag normalflag multiwayflag=(option1 option2 |
| 41 |
+default_option) -default_off_flag". |
| 42 |
|
| 43 |
In use.[local.]desc the multiwayflag description should explain what each |
| 44 |
alternative means. |
| 45 |
|
| 46 |
Marijn |
| 47 |
|
| 48 |
- -- |
| 49 |
Marijn Schouten (hkBst), Gentoo Lisp project |
| 50 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 51 |
-----BEGIN PGP SIGNATURE----- |
| 52 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 53 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 54 |
|
| 55 |
iD8DBQFHC1Xup/VmCx0OL2wRAnrfAJkBLMTuzlpu6g4uhZW6429hJ3gsUgCgr8h7 |
| 56 |
2cX5/qHGbj4Y3GgDCw/uSrk= |
| 57 |
=pVPW |
| 58 |
-----END PGP SIGNATURE----- |
| 59 |
-- |
| 60 |
gentoo-dev@g.o mailing list |
Archives