| 1 |
Hi All, |
| 2 |
|
| 3 |
I've come across a peculiar inconsistency with one tiny aspect of the |
| 4 |
Gentoo Development Policy which would probably bore everyone except for |
| 5 |
the most pedantic and anal developers. |
| 6 |
|
| 7 |
I was reading through the Gentoo Developer HOWTO (aka. Ebuild HOWTO)[1] |
| 8 |
as all developers should (yes, I'm looking at you ;) and found that the |
| 9 |
field IUSE is declared as an optional field. |
| 10 |
|
| 11 |
I've brought this up on gentoo-doc and also on bugzilla[2], but there |
| 12 |
doesn't seem to be any authoritative answer on whether IUSE should be |
| 13 |
included even if a package does not use and USE flags. |
| 14 |
|
| 15 |
From a earlier revision (1.13) of the Developer Policy, it says: |
| 16 |
|
| 17 |
IUSE : This is set to what USE variables your package uses. If your |
| 18 |
package uses none, you must set it to IUSE="". |
| 19 |
|
| 20 |
However, the current document states that: |
| 21 |
|
| 22 |
IUSE : OPT : This is set to whatever USE variables your package |
| 23 |
utilizes. Remember that KEYWORDS should not be listed in here! |
| 24 |
|
| 25 |
(where OPT = optional) |
| 26 |
|
| 27 |
Now, which one is right? Should we include IUSE="" if there are no USE |
| 28 |
variables being used, or should we just remove them? |
| 29 |
|
| 30 |
I don't mind either way, because adding an extra 7 characters to an |
| 31 |
ebuild doesn't do me or a user a great deal of harm. But it would be |
| 32 |
nice to be clear on what the policy should be. |
| 33 |
|
| 34 |
[1] http://www.gentoo.org/doc/en/gentoo-howto.xml |
| 35 |
[2] http://bugs.gentoo.org/show_bug.cgi?id=34131 |
| 36 |
|
| 37 |
Cheers, |
| 38 |
-- |
| 39 |
Alastair 'liquidx' Tse |
| 40 |
>> Gentoo Developer |
| 41 |
>> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/ |
Archives