1 |
On Mon, 13 Jan 2014 15:39:17 +0700 |
2 |
C. Bergström <cbergstrom@×××××××××.com> wrote: |
3 |
|
4 |
> Drive-by trolling comment but I wish the effort to keep porkage alive |
5 |
> would have instead been directed towards pkgcore. |
6 |
|
7 |
If we still have users left by the time pkgcore is finished... |
8 |
|
9 |
Moving the work efforts from one PM to another and expecting the future |
10 |
to go well is too optimistic, of course it would make pkgcore a great |
11 |
thing eventually but it can come at the cost of Gentoo itself; *danger*. |
12 |
|
13 |
While Portage's performance might have dropped a little (though is still |
14 |
quite fast [~30s] on --backtrack=0), the development on it didn't stop |
15 |
as Arfrever and few_ have been committing over the past weeks to months; |
16 |
there just hasn't been a release because the lead position was MIA... |
17 |
|
18 |
And before anyone pulls a "pkgcore almost has EAPI 5 support" comment; |
19 |
you should note that EAPI 6 is around the corner, and many of its |
20 |
would-be features have already been implemented in Portage. |
21 |
|
22 |
I'm in doubt if the same hold true for pkgcore; which was known to be |
23 |
dead for a while as its founder left development, and it took some time |
24 |
for two of our developers to pikc it up again. |
25 |
|
26 |
So, yes, we need more people on pkgcore; no, we can't just leave |
27 |
Portage behind, as it still is the beating heart of Gentoo for now. |
28 |
|
29 |
Who knows, as we get up to speed, Portage might even see some neat |
30 |
refactoring and performance improvements; or well, that's what I expect |
31 |
to see some of us work towards to. We're already putting measures in |
32 |
place to clean up the source code (short variable names, file length); |
33 |
but for now, it's not that huge of a problem to stop using it at all. |
34 |
|
35 |
-- |
36 |
With kind regards, |
37 |
|
38 |
Tom Wijsman (TomWij) |
39 |
Gentoo Developer |
40 |
|
41 |
E-mail address : TomWij@g.o |
42 |
GPG Public Key : 6D34E57D |
43 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |