On Sun, Nov 14, 2010 at 10:22 PM, Jeremy Olexa <darks...@gentoo.org> wrote: > On 11/11/2010 05:00 PM, Matt Turner wrote: >> >> Hi, >> I'd like to begin stabilizing packages on MIPS. I've gotten acks from >> Redhatter, leio, and r0bertz, and Kumba doesn't really care. >> >> What's the best method to go about doing this? Stabilize the system >> packages, then remove ~mips from ACCEPT_KEYWORDS in the profiles? >> Should we target package versions that aren't stabilized on other >> architectures yet, so that we'll have an extended testing period >> before they'll come up for stabilization? That is, can I plan to make >> gcc-4.5.1 or something the first restabilized version of gcc, go ahead >> and begin testing it, and be ready for stabilization when toolchain >> requests it? > > What is the long term plan here? Stable @system set, stable everything > currently ~mips keyworded, or something random in between that? I'd caution > mips keywording here in general as the team is small and seems unlikely to > keep up from my POV. I'm not being negative, just being real. I suppose it > is somewhat possible to keep up if the mips team dropped some ~mips packages > in general and focused on the @system set. > > -Jeremy
I don't have a long-term plan other than to stabilize the base system and provide n32 stages. Where it goes from there, I don't know. There's certainly the potential for new users and developers to join in since Lemote/Gdium hardware is available and in general faster than all but the fastest Linux-supported SGI systems. Though, you'd think with six members of the MIPS herd we'd have enough man-power between us to keep some stable keywords. Matt