1 |
On Mon, Feb 17, 2014 at 2:12 PM, Michał Górny <mgorny@g.o> wrote: |
2 |
> Dnia 2014-02-17, o godz. 13:44:04 |
3 |
> Mike Gilbert <floppym@g.o> napisał(a): |
4 |
> |
5 |
>> Index: python.eclass |
6 |
>> =================================================================== |
7 |
>> RCS file: /var/cvsroot/gentoo-x86/eclass/python.eclass,v |
8 |
>> retrieving revision 1.169 |
9 |
>> diff -u -r1.169 python.eclass |
10 |
>> --- python.eclass 6 Feb 2014 05:34:07 -0000 1.169 |
11 |
>> +++ python.eclass 17 Feb 2014 18:40:31 -0000 |
12 |
>> @@ -35,7 +35,7 @@ |
13 |
>> # focus on converting packages to use the new eclasses. |
14 |
>> |
15 |
>> _CPYTHON2_GLOBALLY_SUPPORTED_ABIS=(2.4 2.5 2.6 2.7) |
16 |
>> -_CPYTHON3_GLOBALLY_SUPPORTED_ABIS=(3.1 3.2 3.3) |
17 |
>> +_CPYTHON3_GLOBALLY_SUPPORTED_ABIS=(3.1 3.2 3.3 3.4) |
18 |
>> _JYTHON_GLOBALLY_SUPPORTED_ABIS=(2.5-jython 2.7-jython) |
19 |
>> _PYPY_GLOBALLY_SUPPORTED_ABIS=(2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9 2.7-pypy-2.0) |
20 |
>> _PYTHON_GLOBALLY_SUPPORTED_ABIS=(${_CPYTHON2_GLOBALLY_SUPPORTED_ABIS[@]} ${_CPYTHON3_GLOBALLY_SUPPORTED_ABIS[@]} ${_JYTHON_GLOBALLY_SUPPORTED_ABIS[@]} ${_PYPY_GLOBALLY_SUPPORTED_ABIS[@]}) |
21 |
> |
22 |
> To be honest, I'm against adding new implementations to the old eclass. |
23 |
> I'm all for letting it rot and not adding extra work on maintaining |
24 |
> ebuilds using it. Since it is opt-out, adding the new implementation |
25 |
> would mean we need to add restrictions to ebuilds. |
26 |
> |
27 |
> Instead, I'd just say that we require the new eclass for py3.4. |
28 |
> |
29 |
|
30 |
That's fine by me, as long as it doesn't break anything. I can't think |
31 |
of any such breakage off the top of my head. |