1 |
* Stuart Jansen [sjansen@×××.edu] [2002-08-13 12:28 -0600]: |
2 |
|
3 |
[snip] |
4 |
> That said, let me say that as a user I've been very frustrated by the |
5 |
> handling of this change. I subscribe to the lists for the very purpose |
6 |
> of being informed of these changes. Unfortunately, the ebuilds |
7 |
> started to change more than four days before the announcement was sent |
8 |
> out. It seems to me this is the opposite of what should have happened. |
9 |
|
10 |
no, the ebuilds have been changed (that is KEYWORDS added) for sometime |
11 |
now (we have been working on it for a month or more .. a HUGE |
12 |
undertaking as each package, and it's dependencies, have to be tested |
13 |
and then keyworded). The use of KEYWORD only came into effect with |
14 |
portage-2.0.2x, we have been holding back these versions of portage |
15 |
(which have been masked) for this very reason, and it should be noted |
16 |
held back when these versions contained significant bug fixes. |
17 |
|
18 |
Now it looks as though portage-2.0.27 has been unmasked, i guess as x86, |
19 |
whom are 100% KEYWORD ready, and the bugfixes have been given priority |
20 |
over ppc readyness. Again this is a HUGE undertaking, and we have tryed |
21 |
to get to a stage where these issues would effect users minimally. |
22 |
|
23 |
Now, on to your complaint. OK prehaps someone should have informed |
24 |
users, however, most (if not all) the devs are running 1.4 (2.0 |
25 |
profiles), this is so we can test this forthcoming release, this profile |
26 |
uses portage-2.0.2x, and so (at least in my case) i was unaware that |
27 |
portage-2.0.27 had in fact been unmasked. Had i known, i would probably |
28 |
have taken time out from other tasks (that is, relocating to .nl, |
29 |
packing, gentoo, eating etc etc) to inform people, but we are human and |
30 |
things slip through the net. |
31 |
|
32 |
We are constantly trying to develop procedure for our practice, |
33 |
developmental, informational, etc and most of the time we get it right, |
34 |
or if not at least improve how we might go about it in future. The |
35 |
move to KEYWORDS will help give us QA and help with the simple problem |
36 |
of sharing the same tree as x86/sparc, both necessary developements to |
37 |
gentoo as a distribution. |
38 |
|
39 |
As with any change there will be teething problems, and we hope that |
40 |
users will work with us on ironing these out. |
41 |
|
42 |
> Now that that's off my chest, I'll see if I have some time to build |
43 |
> and test this evening. Thanks again for making such a wonderful distro |
44 |
> available on ppc. |
45 |
|
46 |
That would be great, tnx in advance |
47 |
|
48 |
best |
49 |
|
50 |
cal |