1 |
Am 16.09.2010 03:46, schrieb Ryan Hill: |
2 |
> On Wed, 15 Sep 2010 19:02:00 +0200 |
3 |
> Thomas Sachau <tommy@g.o> wrote: |
4 |
> |
5 |
>> From discussion on IRC, it seems, like there are different options, so i would like to clarify this |
6 |
>> policy: |
7 |
>> |
8 |
>> The test USE flag is (i am only talking about portage now, since i am most familar with it) an |
9 |
>> internal flag, which is added by portage for every ebuild and enabled/disabled based on |
10 |
>> FEATURES=test or not. It is not managed via USE= line in make.conf or package.use settings. So in |
11 |
>> handling and setting, it is pretty much the same as for the arch USE flags, which are also only |
12 |
>> internally used and added, but never exposed to the users. |
13 |
>> Now i see the opinion, that it should always be added to IUSE, when it is referenced in the ebuild. |
14 |
>> This adds it to the visible USE flags in emerge output (imho pointless, since it is no option, which |
15 |
>> can be enabled/disabled like the other USE flags), but otherwise does change nothing. |
16 |
>> |
17 |
>> Because of this, i would like to discourage the addition of test USE flag to IUSE, since it is just |
18 |
>> an internal USE flag, which should not be exposed to the user. |
19 |
> |
20 |
> Well, it does indicate the presence of optional dependencies. |
21 |
> |
22 |
> I've always thought the test USE flag being forced by FEATURES=test was |
23 |
> messed up. Why can't it be controlled package-by-package, with FEATURES=test |
24 |
> just enabling USE=test by default? |
25 |
> |
26 |
> |
27 |
|
28 |
Controling the test USE flag alone without the test FEATURE is useless, since it wont run the |
29 |
src_test phase. And being able to disable the test USE flag with FEATURES=test will result in |
30 |
missing deps or build-system args. Can you tell me any reason, why you want to expose and control |
31 |
the test USE flag independently of FEATURES=test? |
32 |
|
33 |
-- |
34 |
Thomas Sachau |
35 |
|
36 |
Gentoo Linux Developer |