1 |
2010-11-28 21:15:15 Markos Chandras napisaĆ(a): |
2 |
> On Sun, Nov 28, 2010 at 08:32:16PM +0100, Arfrever Frehtes Taifersar Arahesis wrote: |
3 |
> > I would like to introduce incompatible improvements in syntax of PYTHON_DEPEND variable in |
4 |
> > EAPI >=4. The new syntax will depend on whether given package supports installation for |
5 |
> > multiple Python ABIs. The extended functionality will replace PYTHON_USE_WITH* variables. |
6 |
> > |
7 |
> > [...] |
8 |
> |
9 |
> Your changes are far too complicated to me. Python eclass and |
10 |
> consequently writing python ebuilds is a difficult task already. |
11 |
> If you keep adding more and more "magic" in this eclass, |
12 |
> you will end up supporting and fixing all the python ebuilds by |
13 |
> yourself. Maybe you should consider splitting python eclass |
14 |
> into two separate modules. One for core functionality and |
15 |
> another one which will inherit this core eclass and export |
16 |
> a simple API so the rest of us can use python eclass without |
17 |
> having to study all the documentation for a month. |
18 |
|
19 |
The changes aren't complicated. You only need to understand special "<<>>" marker. |
20 |
The syntax of ranges of versions in packages not supporting installation for multiple Python ABIs |
21 |
won't be changed. Majority of ebuilds won't need to explicitly use any extended functionality |
22 |
of PYTHON_DEPEND. In ebuilds, which support installation for multiple Python ABIs, unconditionally |
23 |
depend on Python and don't need additional USE dependencies on Python, I will unset PYTHON_DEPEND, |
24 |
because it will work like PYTHON_DEPEND="<<>>". |
25 |
|
26 |
-- |
27 |
Arfrever Frehtes Taifersar Arahesis |