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