1 |
On Sun, 2004-05-02 at 12:04 -0500, Lance Albertson wrote: |
2 |
> On Sun, 2004-05-02 at 11:45, Donnie Berkholz wrote: |
3 |
> > On Sun, 2004-05-02 at 09:32, Nathaniel McCallum wrote: |
4 |
> > > On Sun, 2004-05-02 at 07:29 -0400, Kurt Lieber wrote: |
5 |
> > > > * Releases are largely meaningless, comprised of nothing more than package |
6 |
> > > > updates for GRP. |
7 |
> > > |
8 |
> > > Lets use 2004.x quarterly releases to perfect our GRP proceedure and get |
9 |
> > > GRP online. Once we are at that point we can divorce GRP from liveCD |
10 |
> > > releases if we need to. |
11 |
> > |
12 |
> > Exactly what I was thinking when reading this thread. Just provide a |
13 |
> > package+stages CD (or two) quarterly, and let them use a LiveCD from the |
14 |
> > (biannual?) LiveCD release. From what I see, it appears that much of the |
15 |
> > QA time goes into getting the LiveCDs working properly. |
16 |
> |
17 |
> Funny, I was actually just thinking of that last night before I went to |
18 |
> bed. I see that quarterly releases for stages/grp package sets are |
19 |
> needed, but I really don't see a need for quarterly livecd releases. |
20 |
> There needs to be enough time to work out bugs/implement new features, |
21 |
> etc. The only thing that I can see for quarterly releases is driver |
22 |
> upgrades on the kernels used on the livecds. So, that may be debatable. |
23 |
> |
24 |
> Thoughts? |
25 |
|
26 |
The real problem here is not a problem with releng so much as it is a |
27 |
problem with portage. I'm not knocking portage at all, it has served us |
28 |
great thus far. However, having a seperate GRP release is really |
29 |
inconvienient as compared to a binary tree. Most enterprise users and |
30 |
most personal users who don't have a ton of time on their hands, want |
31 |
the ability to build from source if they need too, but to use binaries |
32 |
when they don't. Portage does GREAT at the first, but not so great at |
33 |
the second. If we had a binary tree(s), we could do with more |
34 |
infrequent liveCDs (and a lot less stress on releng). GRP should be a |
35 |
temporary provision until portage has better binary support (notice the |
36 |
emphasis on TEMPORARY). However, there are even some devs talking about |
37 |
canning GRP. This is simply not an option, but neither is making GRP |
38 |
perminant. We need to, once and for all, engineer portage for the |
39 |
greatest possible flexability. Anyway, I know I'll probably get flamed, |
40 |
but as I see it we only have two options kill off GRP or make portage |
41 |
support a binary tree. I've said enough... |
42 |
|
43 |
don_fireproof_suit() |
44 |
Nathaniel |
45 |
|
46 |
|
47 |
-- |
48 |
gentoo-releng@g.o mailing list |