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