Ciaran McCreesh wrote:
Luca Barbato <[EMAIL PROTECTED]> wrote:
I'd suggest something like "if nobody could test your update in a
timely way you should ask and possibly get an account on an arch box
in order to test it and bump if the minimal test pass"
sounds fair?
Sounds like a great way to get more broken packages, which means more
work for arch teams fixing them, which means less time available for
fixing important bugs.
I find it more often we're waiting for the arch team to do something
so we can remove the broken package from the tree. I have four versions
of freetype sitting around that I'd really like to get rid of but can't
until mips stabilizes a newer version. Granted, I may only think it
happens more often because I only see it from the dev side.
I don't mean to rag on the mips team because I understand how difficult
it can be to build and test packages on that type of hardware (see [i]
for a good explanation). I've personally been looking into getting an
Indigo2 or O2 box to help out. I'd like to know, though, if they have
any plans to deal with the current situation. And if there is no real
solution in sight, what can we do about it? Is dropping the
MIPS stable tree an option?
(btw this is a discussion that should take place on the -project ML)
[i] http://permalink.gmane.org/gmane.linux.gentoo.devel/46072
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
--
[EMAIL PROTECTED] mailing list
