1 |
On 10/24/2010 09:49 PM, Arfrever Frehtes Taifersar Arahesis wrote: |
2 |
> 2010-10-18 17:26:13 Petteri Räty napisał(a): |
3 |
>> On 10/18/2010 04:33 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
4 |
>> |
5 |
>>> Subpatch #10 fixes exporting of python_pkg_setup() in EAPI >=4. |
6 |
>>> |
7 |
>>> There will be other changes in API of python.eclass in EAPI >=4, so python.eclass still doesn't |
8 |
>>> support EAPI="4". |
9 |
>>> |
10 |
>> |
11 |
>> EAPI 4 is not approved yet. Ebuilds can't use it yet so I don't think we |
12 |
>> should start migrating eclasses before it's final. |
13 |
> |
14 |
> Porting of python.eclass to EAPI="4" has started some months ago and will take at least |
15 |
> 1 additional month, so it's better to perform it earlier. |
16 |
> |
17 |
|
18 |
Usage of new EAPIs in the tree is not allowed before council approval. |
19 |
|
20 |
Regards, |
21 |
Petteri |