On 29/02/12 08:49, "Paweł Hajdan, Jr." wrote: > On 2/28/12 10:13 PM, Krzysztof Pawlik wrote: >> Highlights: >> - <400 lines of code including documentation >> - should work for >95% of packages (my educated guess) >> - did I mention it's *SIMPLE*? >> - easy to maintain & read so it's also easy to use > > This is awesome! Compare that to over 3000 LOC of python.eclass. :)
Count distutils.eclass too: $ wc -l python-distutils-ng.eclass python.eclass distutils.eclass 364 python-distutils-ng.eclass 3168 python.eclass 592 distutils.eclass >> Important thing: I'm not aiming at having 100% functionality of current >> python.eclass+distutils.eclass in the new one, I think that simplicity is >> more >> important that supporting every possible, obscure case that's out there. > > Exactly. > >> If there are no objections then during the weekend (March 3, 4) I will add >> this >> to portage (after finishing remaining TODO items, PyPy requires 4G of >> RAM(!!)). > > I second this so much (didn't review the eclass in detail, but it's > obviously better than python.eclass). Thank you :) > What's the plan to retire python.eclass? I'm not entirely sure - there's no pressure to migrate off it, both can coexist happily. I don't think it can be retired until be have all functionality from python.eclass+distutils.eclass somewhere (especially tests!). If the package is distutils-based then migration should be pretty painless and new packages (or version/revision bumps) can start using it as soon as it hits portage. -- Krzysztof Pawlik <nelchael at gentoo.org> key id: 0xF6A80E46 desktop-misc, java, vim, kernel, python, apache...
signature.asc
Description: OpenPGP digital signature
