| 1 |
On Sun, 2013-06-16 at 16:44 +0200, Tom Wijsman wrote: |
| 2 |
> On Sun, 16 Jun 2013 06:55:23 -0700 |
| 3 |
> Brian Dolbec <dolsen@g.o> wrote: |
| 4 |
> |
| 5 |
> > I'll take pkgcore (if somehow we can get eapi 5 finished.) |
| 6 |
> |
| 7 |
> Here's the catch: it's not only about finishing EAPI 5, but also about |
| 8 |
> implementing the upcoming EAPI 6 changes and fixing any bugs that arise. |
| 9 |
> |
| 10 |
> For it to be feasible to use it would need an upstream maintainer |
| 11 |
> for that package; it goes a little further than "let's implement X or |
| 12 |
> fix Y", the code has to be understood to gain the necessary insight. |
| 13 |
> |
| 14 |
> If one just hacks in things to make it work, he'll waste efforts. |
| 15 |
> Think before anyone plans to pick this up, it is quite a commitment. |
| 16 |
> |
| 17 |
> http://c2.com/cgi/wiki?LegacyCode |
| 18 |
> |
| 19 |
> http://www.amazon.com/books/dp/0131177052 |
| 20 |
> |
| 21 |
> I sincerely have interest in working on a heavily refactored PM or a PM |
| 22 |
> from scratch; but, I can't see myself pick up a big Python project as |
| 23 |
> I'm not really used to anything beyond average Python scripts. Or maybe |
| 24 |
> I'm afraid of nothing, I can't tell in advance not knowing its code. |
| 25 |
> |
| 26 |
> I'll take it into consideration though; there is quite a huge choice |
| 27 |
> between applying software re-engineering practices (mostly reverse |
| 28 |
> engineering) to pkgcore, applying those practices (mostly refactoring) |
| 29 |
> to Portage or implementing an all new PM from scratch. |
| 30 |
> |
| 31 |
|
| 32 |
Thank you for considering helping. I have stayed away form the |
| 33 |
intricate details of package management in the past, but I also do not |
| 34 |
like how long portage is taking now for dep calculations. So, I am |
| 35 |
going to look into what it needs to be completed. I know there are |
| 36 |
others out there that would also like to see pkgcore keep going. If we |
| 37 |
(that means I want help, so please speak up) can get EAPI 5 finished. |
| 38 |
Then EAPI 6 will be that much easier when the time comes, which is |
| 39 |
hopefully not too soon. |
| 40 |
|
| 41 |
For the record, I have admin capability to pkgcore's repo, so if we can |
| 42 |
get things ironed out. It will be possible to push the changes to the |
| 43 |
main repo and release it. But, I also admit that pkgcore may have to |
| 44 |
move to an overlay to get it up to speed with current required |
| 45 |
functionality. |
Archives