The above package has been found to use FEATURES in at least one of its ebuilds. FEATURES is a portage specific package manager configuration variable not specified in PMS and cannot reliably be used in ebuilds or eclasses. Usually there are a number of ways to achieve the same thing though. In other cases, the usage of FEATURES in the ebuild is simply invalid. If you need to check whether "test" is in ${FEATURES}, you can test if the USE flag "test" is set, since it will be activated in that case. When you check for "userpriv" in ${FEATURES} you may be able to something like the following instead: if [[ ${EUID} -eq 0 ]]; then rootstuff else nonrootstuff fi Thanks
Created attachment 225467 [details, diff] Replace check for test in $FEATURES by check for test use flag.
Comment on attachment 225467 [details, diff] Replace check for test in $FEATURES by check for test use flag. The attached patch fix the QA problem.
And while we're at it, why does it have a src_test() that does an einfo instead of RESTRICT=test like it should?
InCVS
