1 |
El lun, 27-05-2013 a las 11:35 -0400, Jonathan Callen escribió: |
2 |
> A quick reminder for anyone using python-r1.eclass or |
3 |
> python-single-r1.eclass: |
4 |
> |
5 |
> These eclasses provide a ${PYTHON_REQUIRED_USE} variable that should |
6 |
> be included in REQUIRED_USE under the same USE conditionals (if any) |
7 |
> that ${PYTHON_DEPS} is included in DEPEND/RDEPEND. |
8 |
> |
9 |
> For example, if your ebuild has: |
10 |
> |
11 |
> RDEPEND=" |
12 |
> python? ( ${PYTHON_DEPS} |
13 |
> " |
14 |
> |
15 |
> then you should also have: |
16 |
> |
17 |
> REQUIRED_USE=" |
18 |
> python? ( ${PYTHON_REQUIRED_USE} ) |
19 |
> " |
20 |
> |
21 |
> And if your ebuild just has: |
22 |
> |
23 |
> RDEPEND="${PYTHON_DEPS}" |
24 |
> |
25 |
> then you should also have: |
26 |
> |
27 |
> REQUIRED_USE="${PYTHON_REQUIRED_USE}" |
28 |
> |
29 |
> Failure to include these in REQUIRED_USE may cause the eclass to die |
30 |
> very late in the build process. |
31 |
> |
32 |
> Thank you, |
33 |
> |
34 |
> Jonathan Callen |
35 |
|
36 |
Couldn't a repoman check be added for warning when an ebuild using that |
37 |
eclasses don't set REQUIRED_USE at all? |