| Summary: | sys-cluster/mpich2-1.0.3-r1 FEATURES misuse (test) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thilo Bangert (RETIRED) (RETIRED) <bangert> |
| Component: | New packages | Assignee: | Justin Bronder (RETIRED) <jsbronder> |
| Status: | RESOLVED FIXED | ||
| Severity: | QA | CC: | hp-cluster |
| Priority: | High | Keywords: | QAcanfix |
| Version: | 1.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 266409 | ||
| Bug Blocks: | 174335 | ||
This version is gone as soon as 1.0.8 is stable. sys-cluster/mpich2-1.0.3-r1 has been removed from the tree. |
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