Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] About current ppc/ppc64 status
Date: Fri, 25 Jul 2014 19:28:48
Message-Id: 1406316517.20388.22.camel@gentoo.org
1 Hello
2
3 With last gnome maintained packages stabilization round I noticed some
4 pending stabilizations/keywordings for really a long time waiting for
5 ppc* teams. For example:
6 https://bugs.gentoo.org/show_bug.cgi?id=470768 -> it's waiting for more
7 than a year and it's blocking from dropping old versions for so long
8 https://bugs.gentoo.org/show_bug.cgi?id=508006 -> the same case, and we
9 cannot drop that stable keywords because looks like ppc team still wants
10 to keep kde in stable
11
12 Then, I finally needed to ask Agostino for help because of that and I
13 wondered if there are some kind of issue in this teams, if they are
14 still able to keep ppc* as stable arches or... :/
15
16 I see two options:
17 - Move ppc* to testing only -> I guess some people will disagree as this
18 architecture is not so old and probably it's still used by enough people
19 - Clarify what packages do they really want in stable.
20
21 The problem of all this is that, as it is shown in this concrete
22 example, if they want to keep, for example, KDE in stable, they will
23 need to also be fast enough for other dependencies. If not, we could go
24 with the "package-per-package" proposal that was approved one year ago
25 by the Council for alpha/ia64.
26
27 But the problem of "package-per-package" proposal is shown in:
28 https://bugs.gentoo.org/show_bug.cgi?id=470768#c9
29
30 Once we start dropping stable keyword in one package, we need to do the
31 same in reverse-deps, that will also have other reverse-deps... and that
32 it ends up being a lot of work arch teams cannot accomplish (as they are
33 the same teams that are so overloaded that cannot keep stabilizing fast
34 enough) and things get blocked forever :(
35
36 That is the reason for me thinking that maybe the way to go would be to
37 do the opposite -> keep only base-system and a few others stable and
38 drop stable for most of the rest. This big effort could be accomplished
39 in a week by other developers willing to help (like me) and would solve
40 the issue for the long term. I guess that is what HPPA team did in the
41 past and I think it's working pretty well for them (in summary, have a
42 stable tree they are able to keep stable). That will also help people in
43 ppc* teams to know that the remaining stabilization bugs, apart of being
44 much less, are important enough to deserve rapid attention, as opposed
45 to current situation that will have some important bugs mixed with tons
46 of stabilization requests of apps that got ppc stable keywords years ago
47 and are currently no so important.
48
49 Thanks a lot

Replies

Subject Author
Re: [gentoo-dev] About current ppc/ppc64 status "Anthony G. Basile" <blueness@g.o>