1 |
On 09/15/2010 08:02 PM, Thomas Sachau wrote: |
2 |
> From discussion on IRC, it seems, like there are different options, so i would like to clarify this |
3 |
> policy: |
4 |
> |
5 |
> The test USE flag is (i am only talking about portage now, since i am most familar with it) an |
6 |
> internal flag, which is added by portage for every ebuild and enabled/disabled based on |
7 |
> FEATURES=test or not. It is not managed via USE= line in make.conf or package.use settings. So in |
8 |
> handling and setting, it is pretty much the same as for the arch USE flags, which are also only |
9 |
> internally used and added, but never exposed to the users. |
10 |
> Now i see the opinion, that it should always be added to IUSE, when it is referenced in the ebuild. |
11 |
> This adds it to the visible USE flags in emerge output (imho pointless, since it is no option, which |
12 |
> can be enabled/disabled like the other USE flags), but otherwise does change nothing. |
13 |
> |
14 |
> Because of this, i would like to discourage the addition of test USE flag to IUSE, since it is just |
15 |
> an internal USE flag, which should not be exposed to the user. |
16 |
|
17 |
Of course it should be exposed to user, it makes reading deptree a lot |
18 |
easier and helps resolving e.g. circular dependencies by temporarily |
19 |
disabling the flag for say, random dev-perl package. |
20 |
|
21 |
But it would be nice if we wouldn't have to add it manually to the IUSE |
22 |
list, but Portage would do it for us. |
23 |
|
24 |
But at any rate, it needs to be visible. |