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