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