1 |
On Sat, 11 May 2013 19:11:23 -0400 |
2 |
Mike Gilbert <floppym@g.o> wrote: |
3 |
|
4 |
> I think this is the safe/conservative method of implementing a |
5 |
> required-use check in the -r1 eclasses. |
6 |
> |
7 |
> Just like with PYTHON_DEPS, we leave it to the ebuild author to |
8 |
> utilize the value by adding it to REQUIRED_USE. I will certainly |
9 |
> assist in the mass-update that will be necessary to implement this in |
10 |
> existing ebuilds. This does not need to be done immediately. |
11 |
> |
12 |
> The PYTHON_REQUIRED_USE name may cause a bit of confusion with the |
13 |
> PYTHON_REQ_USE variable, but I think the latter was a poor naming |
14 |
> choice to begin with. |
15 |
|
16 |
Please update python-single-r1 too. |
17 |
|
18 |
-- |
19 |
Best regards, |
20 |
Michał Górny |