| 1 |
On Wed, 15 Sep 2010 19:02:00 +0200 |
| 2 |
Thomas Sachau <tommy@g.o> wrote: |
| 3 |
|
| 4 |
> From discussion on IRC, it seems, like there are different options, so i would like to clarify this |
| 5 |
> policy: |
| 6 |
> |
| 7 |
> The test USE flag is (i am only talking about portage now, since i am most familar with it) an |
| 8 |
> internal flag, which is added by portage for every ebuild and enabled/disabled based on |
| 9 |
> FEATURES=test or not. It is not managed via USE= line in make.conf or package.use settings. So in |
| 10 |
> handling and setting, it is pretty much the same as for the arch USE flags, which are also only |
| 11 |
> internally used and added, but never exposed to the users. |
| 12 |
> Now i see the opinion, that it should always be added to IUSE, when it is referenced in the ebuild. |
| 13 |
> This adds it to the visible USE flags in emerge output (imho pointless, since it is no option, which |
| 14 |
> can be enabled/disabled like the other USE flags), but otherwise does change nothing. |
| 15 |
> |
| 16 |
> Because of this, i would like to discourage the addition of test USE flag to IUSE, since it is just |
| 17 |
> an internal USE flag, which should not be exposed to the user. |
| 18 |
|
| 19 |
Well, it does indicate the presence of optional dependencies. |
| 20 |
|
| 21 |
I've always thought the test USE flag being forced by FEATURES=test was |
| 22 |
messed up. Why can't it be controlled package-by-package, with FEATURES=test |
| 23 |
just enabling USE=test by default? |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
fonts, gcc-porting, we hold our breath, we spin around the world |
| 28 |
toolchain, wxwidgets you and me cling to the outside of the earth |
| 29 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives