1 |
On Sun, 16 Jun 2013 06:55:23 -0700 |
2 |
Brian Dolbec <dolsen@g.o> wrote: |
3 |
|
4 |
> I'll take pkgcore (if somehow we can get eapi 5 finished.) |
5 |
|
6 |
Here's the catch: it's not only about finishing EAPI 5, but also about |
7 |
implementing the upcoming EAPI 6 changes and fixing any bugs that arise. |
8 |
|
9 |
For it to be feasible to use it would need an upstream maintainer |
10 |
for that package; it goes a little further than "let's implement X or |
11 |
fix Y", the code has to be understood to gain the necessary insight. |
12 |
|
13 |
If one just hacks in things to make it work, he'll waste efforts. |
14 |
Think before anyone plans to pick this up, it is quite a commitment. |
15 |
|
16 |
http://c2.com/cgi/wiki?LegacyCode |
17 |
|
18 |
http://www.amazon.com/books/dp/0131177052 |
19 |
|
20 |
I sincerely have interest in working on a heavily refactored PM or a PM |
21 |
from scratch; but, I can't see myself pick up a big Python project as |
22 |
I'm not really used to anything beyond average Python scripts. Or maybe |
23 |
I'm afraid of nothing, I can't tell in advance not knowing its code. |
24 |
|
25 |
I'll take it into consideration though; there is quite a huge choice |
26 |
between applying software re-engineering practices (mostly reverse |
27 |
engineering) to pkgcore, applying those practices (mostly refactoring) |
28 |
to Portage or implementing an all new PM from scratch. |
29 |
|
30 |
-- |
31 |
With kind regards, |
32 |
|
33 |
Tom Wijsman (TomWij) |
34 |
Gentoo Developer |
35 |
|
36 |
E-mail address : TomWij@g.o |
37 |
GPG Public Key : 6D34E57D |
38 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |