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