| 1 |
On Thu, 03 May 2007 12:15:45 +0200 |
| 2 |
"José Luis Rivero (yoswink)" <yoswink@g.o> wrote: |
| 3 |
> Ehm, IMHO call it discriminate is a big hard. Are the gnome-2.18 or |
| 4 |
> beryl users discriminated or they should be using something different |
| 5 |
> to Gentoo? They only thing people have to do is use some ~arch branch |
| 6 |
> packages, which isn't too difficult (in Gentoo). |
| 7 |
|
| 8 |
No no no. |
| 9 |
In my example we can only use one version of the game with the upstream |
| 10 |
servers. There is only 1 upstream server, we have to use it. |
| 11 |
|
| 12 |
So if it supports 6 archs and some of the arch teams take a few months |
| 13 |
to mark it stable then the chances are it will be out of date anyway |
| 14 |
and the "slacker arches" will never have a stable keyword. |
| 15 |
|
| 16 |
So remove the onus on slacker arches making games stable I just don't |
| 17 |
bother with the stable keyword for network games ever. |
| 18 |
|
| 19 |
Gnome-2.18 on the other hand is a desktop product with zero upstream |
| 20 |
interaction except with programs that have clearly defined protocols |
| 21 |
and are normally backwards compatible. Like say HTTP |
| 22 |
|
| 23 |
> |
| 24 |
> This is how I see it: |
| 25 |
> |
| 26 |
> Problem with keywording straight to stable is that arch teams are |
| 27 |
> very zealous about our stable branch. We put a lot of time trying |
| 28 |
> things to not fail in stable, and if an app is broken, we prefer to |
| 29 |
> not force the users to compile and install another broken (or unknown |
| 30 |
> to be broken) version and work to fix the current stable (patches or |
| 31 |
> bumping) together with the maintainer. |
| 32 |
|
| 33 |
Right, but if stable client version != stable usptream server version |
| 34 |
it cannot be used anyway, making the stable keyword here a bit of a |
| 35 |
joke. |
| 36 |
|
| 37 |
> But if you send things, that you can't try, to stable, the qa baby |
| 38 |
> jesus will cry if it fails, because nobody has taken care of even |
| 39 |
> compile it in the arch :) |
| 40 |
|
| 41 |
Well, that's up to the arch teams I guess. Lots of things fail randomly |
| 42 |
on g/fbsd because of a patch added to fix a linux bug. Maybe when we |
| 43 |
g/fbsd gets a stable branch then we'll come down on the linux |
| 44 |
developers like a ton of bricks :) |
| 45 |
|
| 46 |
Thanks |
| 47 |
|
| 48 |
Roy |
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives