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
there's no package called "media-sound"
thanks
Since the ebuild in question doesn't check either of those, is there an appropriate way to check for collision-protect or not?
collision protection is a packagemanager feature. ebuilds should not know anything about it at all... fix, whatever is causing the collision instead. another, only slightly better workaround is to block on those packages, which install files of the same name. a real fix, like renaming the colliding files, would be preferred. (see also http://blog.flameeyes.eu/2008/12/28/blockers-abuse) thanks
Removed.
