Currently, there seem to be at least a few ebuilds that when doing their tests, need *more* in the way of dependancies when they don't do their tests. There's a local USE variable "makecheck" that a few ebuilds seem to be using, but this doesn't seem to be consistent at all. (someone might enable FEATURES="maketest" but not know about the makecheck variable). One proposed solution by axxo was to make FEATURES="maketest" enable some USE variable that we can then use in DEPENDS. Thoughts?
Why no making it mandatory to add them to DEPEND, instead increasing complexity? The wonderland of features and use flags is getting big.
kdemultimedia-3.3.0, kdenetwork-3.3.0 and swig-1.3.21 failed during test phase if FEATURES="maketest" is activated.
This seems rather old, but it would be very usefull... at least to me. The app-text/tetex ebuild requires a running X (and hence X installed) to complete make check (maketest). But it seems to be too much overhead to add X to DEPEND for tetex (many users won't like that X is pulled in just because of maketest).
*** Bug 122382 has been marked as a duplicate of this bug. ***
TESTDEPEND on its own doesn't cut it. SRC_URI additions are sometimes required as well.
FEATURES=test now implies USE=test in r5551.
This has been released in 2.1.2_rc4-r9.
