| 1 |
Am 16.09.2010 04:01, schrieb Samuli Suominen: |
| 2 |
> On 09/15/2010 08:02 PM, Thomas Sachau wrote: |
| 3 |
>> From discussion on IRC, it seems, like there are different options, so i would like to clarify this |
| 4 |
>> policy: |
| 5 |
>> |
| 6 |
>> The test USE flag is (i am only talking about portage now, since i am most familar with it) an |
| 7 |
>> internal flag, which is added by portage for every ebuild and enabled/disabled based on |
| 8 |
>> FEATURES=test or not. It is not managed via USE= line in make.conf or package.use settings. So in |
| 9 |
>> handling and setting, it is pretty much the same as for the arch USE flags, which are also only |
| 10 |
>> internally used and added, but never exposed to the users. |
| 11 |
>> Now i see the opinion, that it should always be added to IUSE, when it is referenced in the ebuild. |
| 12 |
>> This adds it to the visible USE flags in emerge output (imho pointless, since it is no option, which |
| 13 |
>> can be enabled/disabled like the other USE flags), but otherwise does change nothing. |
| 14 |
>> |
| 15 |
>> Because of this, i would like to discourage the addition of test USE flag to IUSE, since it is just |
| 16 |
>> an internal USE flag, which should not be exposed to the user. |
| 17 |
> |
| 18 |
> Of course it should be exposed to user, it makes reading deptree a lot |
| 19 |
> easier and helps resolving e.g. circular dependencies by temporarily |
| 20 |
> disabling the flag for say, random dev-perl package. |
| 21 |
|
| 22 |
Which deptree are you talking about? The --tree output of portage does not show you any USE flag |
| 23 |
conditionals. Additionally, if you disable the flag with FEATURES=test enabled, test phases will |
| 24 |
fail, so those packages will fail to install, i dont think, that this is the better option. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Thomas Sachau |
| 29 |
|
| 30 |
Gentoo Linux Developer |
Archives