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