Often when using tatt (arch testing tool), or indeed any other automated method for testing ebuilds, I don't have any preference in a clean chroot for how this package should be configured -- I just want tests to run. When running e.g. FEATURES=test emerge -v1 sys-libs/db, we get: ``` # FEATURES=test emerge -v1a sys-libs/db These are the packages that would be merged, in order: Calculating dependencies / !!! Problem resolving dependencies for sys-libs/db ... done! !!! The ebuild selected to satisfy "sys-libs/db" has unmet requirements. - sys-libs/db-6.0.35-r2::gentoo USE="test -cxx -doc -examples -java -tcl" ABI_X86="(64) -32 (-x32)" The following REQUIRED_USE flag constraints are unsatisfied: test? ( tcl ) ``` In a chroot or testing environment, having Tcl on won't bother me, but I do really want those tests to run. To find some other simple examples of this, you can run: qgrep -e "REQUIRED_USE.*test?"
I agree but not just for test, there are a lot of packages that can't be automatically tested because of REQUIRED_USE
