On Thu, 2007-05-03 at 13:11 +0200, Matthias Langer wrote: > > ok, agreed, this is a valid point. so i would suggest, that maintainers > of games where this argument applies, come to special agreements with > the arch teams - or just file bugreports like this: > > " > although games-foo/lord-of-bar-2.4.6 has just been bumped, i would like > to have it stable real soon, as upstream has changed the network > protocol. i have x86 and amd64 hardware available, and can confirm, that > the game works nice there; so, if no one objects, i'm gonna mark > lord-of-bar-2.4.6 stable on x86 and amd64 in two days. i would also like > to have a shiny sparc keyword, but have no hardware to test. so it would > be highly appreciated if someone from the sparc team can give the game a > try. > " >
I can't speak for all of sparc, of course, but generally we try to accommodate requests when the package developers explain the situation. In a case like Eternal Lands, it might turn out that the best solution would be always to keep it as ~sparc, but that would have the same effect in practice as a stable keyword, because anyone playing the game on sparc would know what was going on (I would think). The key here is the bug report, and at that point the friendly sparc developers would work with you. :) > but committing straight to stable on arches where the package wasn't > even tested is an absolute no-do for me. > > > DISCLAIMER: I've not read the bug mentioned as I've lost the email > > with it's number so I may just be talking out of my ass. > > no, in fact you are the first one that comes up with a valid argument, > why games sometimes should go to stable almost immediately. sad, but > true... > Regards, -- Ferris McCormick (P44646, MI) <[EMAIL PROTECTED]> Developer, Gentoo Linux (Devrel, Sparc)
signature.asc
Description: This is a digitally signed message part