1 |
El vie, 25-07-2014 a las 15:07 -0500, William Hubbs escribió: |
2 |
> On Fri, Jul 25, 2014 at 03:57:20PM -0400, Anthony G. Basile wrote: |
3 |
> > On 07/25/14 15:50, Pacho Ramos wrote: |
4 |
> > > El vie, 25-07-2014 a las 15:38 -0400, Anthony G. Basile escribió: |
5 |
> > >> On 07/25/14 15:28, Pacho Ramos wrote: |
6 |
> > >>> That is the reason for me thinking that maybe the way to go would be to |
7 |
> > >>> do the opposite -> keep only base-system and a few others stable and |
8 |
> > >>> drop stable for most of the rest. This big effort could be accomplished |
9 |
> > >>> in a week by other developers willing to help (like me) and would solve |
10 |
> > >>> the issue for the long term. I guess that is what HPPA team did in the |
11 |
> > >>> past and I think it's working pretty well for them (in summary, have a |
12 |
> > >>> stable tree they are able to keep stable). That will also help people in |
13 |
> > >>> ppc* teams to know that the remaining stabilization bugs, apart of being |
14 |
> > >>> much less, are important enough to deserve rapid attention, as opposed |
15 |
> > >>> to current situation that will have some important bugs mixed with tons |
16 |
> > >>> of stabilization requests of apps that got ppc stable keywords years ago |
17 |
> > >>> and are currently no so important. |
18 |
> > >>> |
19 |
> > >> Yes, please let's just do base system stable. I've been randomly taking |
20 |
> > >> care of ppc but nothing systematic. Its pretty spotty. But at the same |
21 |
> > >> time I don't like the idea of just loosing all the stabilization effort |
22 |
> > >> on the base system, so that might work best. Something to think about |
23 |
> > >> for mips too. |
24 |
> > >> |
25 |
> > >> |
26 |
> > > Nice, one think we would need to discuss is what do we consider base |
27 |
> > > system :/ |
28 |
> > > |
29 |
> > > I guess packages maintained by base-system, toolchain and... xorg-server |
30 |
> > > and co... what more |
31 |
> > > |
32 |
> > > Not sure if we could have a list of current stable tree for ppc*, once |
33 |
> > > do we have that list, ppc* teams can drop from that list what they want |
34 |
> > > and we get a new list that will be the final result. What do you think |
35 |
> > > about that? |
36 |
> > > |
37 |
> > > |
38 |
> > |
39 |
> > At the very least, its what's needed to build the stages with catalyst. |
40 |
> > I would think we should start with base/packages, but I don't want to |
41 |
> > limit it to just those because I at least need a more for building and |
42 |
> > maintaining. Where should we start to compile such a list? |
43 |
> |
44 |
> If we are going to do this, I think we should drop these arch's |
45 |
> to exp status in the profiles. That way, it keeps repoman from bothering |
46 |
> the rest of us about stabilizations, and we don't have to worry about |
47 |
> filing stable requests on them. |
48 |
> |
49 |
> That would let you stabilize things that you need to build the stages. |
50 |
> |
51 |
> William |
52 |
> |
53 |
|
54 |
But, moving ppc* to exp wouldn't lead us to likely break their tree? |
55 |
(because we wouldn't get any dependency issue even with "base" |
56 |
packages...) |