| Summary: | app-forensics/zzuf FEATURES misuse (sandbox) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thilo Bangert (RETIRED) (RETIRED) <bangert> |
| Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | QA | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 174335 | ||
Thanks, fixed in CVS. + 31 Oct 2012; Michael Palimaka <kensington@gentoo.org> zzuf-0.13-r1.ebuild: + Restrict tests that fail with sandbox enabled, wrt bug #279465. Migrate to + EAPI 4. |
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