1 |
On Thu, 2014-01-09 at 17:52 -0800, Patrick McLean wrote: |
2 |
> On Fri, 10 Jan 2014 02:19:03 +0100 |
3 |
> Tom Wijsman <TomWij@g.o> wrote: |
4 |
> |
5 |
> > On Fri, 10 Jan 2014 08:31:21 +0800 |
6 |
> > Patrick Lauer <patrick@g.o> wrote: |
7 |
> > |
8 |
> > > On 01/10/2014 08:16 AM, heroxbd@g.o wrote: |
9 |
> > > Last I checked paludis wasn't faster - on average portage was a few |
10 |
> > > percents faster. |
11 |
> > |
12 |
> |
13 |
> > > For python things you really want python or C instead of C++... |
14 |
> > |
15 |
> > Why is this a Python thing? What's the reason to exclude a language? |
16 |
> > |
17 |
> > > So, what you wanted to ask was: |
18 |
> > > "Which parts of pkgcore can be migrated into portage?" |
19 |
> > |
20 |
> > Or rather: "What does it take to migrate parts of pkgcore into |
21 |
> > portage?" |
22 |
> |
23 |
> Why not just switch to using pkgcore as the default package manager. |
24 |
> radhermit has been doing a lot of work lately getting EAPI 5 support |
25 |
> added, and generally fixing bugs etc. |
26 |
> |
27 |
> Since we no longer have anyone intimately familiar with the |
28 |
> portage code, we should just switch to a more modern and readable |
29 |
> system. Rather than having random people trying to learn the convoluted |
30 |
> portage code, let's concentrate on getting pkgcore to a point where |
31 |
> we can replace portage with it. |
32 |
> |
33 |
|
34 |
Patrick If you wish to be a part of getting pkgcore's eapi 5 fully |
35 |
working your welcome to start helping out. I can set you up with access |
36 |
in the main google code repo. Radhermit has been working mostly out of |
37 |
his github account, updating the main repo. |
38 |
|
39 |
I would very much love to get pkgcore fully functional in eapi 5. |
40 |
|
41 |
It's speed runs circles around portage and paludis. |
42 |
|
43 |
I have not been able to help radhermit out as yet, I have been trying to |
44 |
get some other project cleaned up before delving deeper into pkgcore |
45 |
code. I have just recently taken over lead of portage (an interim |
46 |
position) due to Zac stepping down and away. So I have that added to my |
47 |
todo list at the moment too. |
48 |
|
49 |
-- |
50 |
Brian Dolbec <dolsen@g.o> |