| 1 |
Roy Marples wrote: |
| 2 |
> |
| 3 |
> I maintain and play a game called Eternal Lands. I'm a Council member, |
| 4 |
> but not part of the games team/herd. |
| 5 |
> |
| 6 |
> One of the problems games have with stable/unstable/testing/whatever |
| 7 |
> keywords is that upstream changes things that in any other application |
| 8 |
> just would not change. For example, the network protocol when talking |
| 9 |
> to servers. EL is very version specific and when a new client is |
| 10 |
> launched, around once every 6 months they change over right away. That |
| 11 |
> means our users need the game right away. |
| 12 |
|
| 13 |
Thanks for the example, trust me if I tell you that we can understand |
| 14 |
the situation pretty well. |
| 15 |
|
| 16 |
> |
| 17 |
> I used to commit EL straight to stable for this very reason, but now |
| 18 |
> after a few Gentoo QA people bitched EL will never ever have a stable |
| 19 |
> keyword. |
| 20 |
|
| 21 |
I'm nearly sure that you always (at least) compile and run the new |
| 22 |
version in your box before you sent it to stable, didn't you? So, at |
| 23 |
least, you are able to say that it works in your case. |
| 24 |
|
| 25 |
> So instead I periodically have to let our users know how to |
| 26 |
> unmask EL just so they can play their game. |
| 27 |
|
| 28 |
There are always ways to educate users about how to use portage properly. |
| 29 |
|
| 30 |
> So no, in many cases NOT committing straight to stable CAN be |
| 31 |
> detrimental to our users if all they want is a games machine. You could |
| 32 |
> argue that they shouldn't be using Gentoo, but I would argue why should |
| 33 |
> we discriminate? |
| 34 |
> |
| 35 |
|
| 36 |
Ehm, IMHO call it discriminate is a big hard. Are the gnome-2.18 or |
| 37 |
beryl users discriminated or they should be using something different to |
| 38 |
Gentoo? They only thing people have to do is use some ~arch branch |
| 39 |
packages, which isn't too difficult (in Gentoo). |
| 40 |
|
| 41 |
This is how I see it: |
| 42 |
|
| 43 |
Problem with keywording straight to stable is that arch teams are very |
| 44 |
zealous about our stable branch. We put a lot of time trying things to |
| 45 |
not fail in stable, and if an app is broken, we prefer to not force the |
| 46 |
users to compile and install another broken (or unknown to be broken) |
| 47 |
version and work to fix the current stable (patches or bumping) together |
| 48 |
with the maintainer. |
| 49 |
|
| 50 |
But if you send things, that you can't try, to stable, the qa baby jesus |
| 51 |
will cry if it fails, because nobody has taken care of even compile it |
| 52 |
in the arch :) |
| 53 |
|
| 54 |
Games are not part of core system, so IMHO, use the ~arch branch to have |
| 55 |
the latest cool version to enjoy, could be a good way to go for those |
| 56 |
el1te gam3rs. |
| 57 |
|
| 58 |
Thanks. |
| 59 |
|
| 60 |
-- |
| 61 |
Jose Luis Rivero <yoswink@g.o> |
| 62 |
Gentoo/Doc Gentoo/Alpha |
| 63 |
-- |
| 64 |
gentoo-dev@g.o mailing list |
Archives