The above package has been found to use FEATURES in at least one of its ebuilds. affected ebuilds: mono-1.2.5.1-r1.ebuild: hasq test $FEATURES && die "Make check failed. See above for details." mono-1.2.5.1-r1.ebuild: hasq test $FEATURES || eerror "Make check failed. See above for details." mono-1.2.6-r3.ebuild: hasq test $FEATURES && die "Make check failed. See above for details." mono-1.2.6-r3.ebuild: hasq test $FEATURES || eerror "Make check failed. See above for details." mono-2.0.1-r1.ebuild: hasq test $FEATURES && die "Make check failed. See above for details." mono-2.0.1-r1.ebuild: hasq test $FEATURES || eerror "Make check failed. See above for details." If this has been fixed for more recent versions of the package, please leave this bug open until all older versions have been removed from the tree. 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
Feel free to go ahead and fix them if you want :-) Thanks
Believe this to be fixed as the those ebuilds have been treecleaned.
