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