1 |
On Wed, 2008-01-09 at 02:47 +0000, Ciaran McCreesh wrote: |
2 |
> On Tue, 8 Jan 2008 18:44:22 -0800 |
3 |
> "Alec Warner" <antarus@g.o> wrote: |
4 |
> > > Uh... So where do the original problems come from? Are you saying |
5 |
> > > that packages mysteriously start breaking on their own because |
6 |
> > > no-one's maintaining them? |
7 |
> > |
8 |
> > Of course they do |
9 |
> |
10 |
> Ah, right. Because of the magical elf that lives in the CVS server |
11 |
> that mysteriously goes around breaking dependencies when no-one's |
12 |
> looking. |
13 |
> |
14 |
> Yes, a magical elf. Much more plausible than the theory that it's |
15 |
> actually developers screwing up by dropping keywords or best keyworded |
16 |
> version on a package's deps. |
17 |
|
18 |
Actually, nobody ever said anything about things that magically break. |
19 |
It's more the things like ebuilds with bad code that can't really be |
20 |
changed without a revision bump, which would also require the arch team |
21 |
in question to ACTUALLY DO SOMETHING to make stable. |
22 |
|
23 |
Seriously, your thinly-veiled attempts at deflecting the conversation to |
24 |
something that supports your pithy points is laughable. |
25 |
|
26 |
The issue that was raised is that certain arch teams are incapable of |
27 |
keeping up with the minimal workload they already have and what should |
28 |
be done about it. We want the Council to do something about this issue. |
29 |
You can deny the issue all that you want or try to deflect conversation |
30 |
from the actual issue, but your opinion isn't very important to the much |
31 |
of the current developer pool, seeing as how it doesn't affect you in |
32 |
any way, having been thrown from the project, and all. |
33 |
|
34 |
Now, if you have something possibly constructive to add to this |
35 |
conversation, as a user, feel free, but don't pretend like you're still |
36 |
a member of the mips team. You're not. |
37 |
|
38 |
-- |
39 |
Chris Gianelloni |
40 |
Release Engineering Strategic Lead |
41 |
Alpha/AMD64/x86 Architecture Teams |
42 |
Games Developer |