Re: [gentoo-dev] Restabilizing MIPS
On Sun, Nov 14, 2010 at 10:22 PM, Jeremy Olexa 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
Re: [gentoo-dev] Restabilizing MIPS
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
Re: [gentoo-dev] Restabilizing MIPS
On Thu, Nov 11, 2010 at 6:13 PM, Robin H. Johnson wrote: > On Thu, Nov 11, 2010 at 06:00:00PM -0500, Matt Turner wrote: >> I'd like to begin stabilizing packages on MIPS. I've gotten acks from >> Redhatter, leio, and r0bertz, and Kumba doesn't really care. > Out of interest, what MIPS hardware do you have? I have a Broadcom BCM91250a with a dual-core 800 MHz SiByte CPU and a 200 MHz O2 with 1 GB RAM. See http://mattst88.com/computers/bcm91250a/ . I need to post some pictures, but that'll have to be for later. Matt
Re: [gentoo-dev] Restabilizing MIPS
On Thu, Nov 11, 2010 at 06:00:00PM -0500, 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? I'd be waiting until you can do an `emerge system` and come up with a contemporary build without, before dropping ~mips from the profile. At the moment, I think if you were to try it now, you'd be told it can't be done because of packages being masked by unstable keywords. > 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? I'd certainly aim for the highest available version... as by the time we get ready to keyword it, it'll be the highest stable version, perhaps one version behind. I've been experimenting with KDE 4.5.3 ... or rather, it was 4.5.0 and in package.mask when I started... then I hit issues with qt-webkit that seem to be binutils related. Now that I've got that sorted, I've only now just got KDE built and installed... and it looks as if I'll be doing rebuilds of it to try and chase out some bugs. That said, don't focus all your attention on the bleeding edge, be prepared to take a step back. At my old workplace, I recall porting kernel git HEAD (2.6.35-rc? at the time) to an ARM platform and experiencing various issues... I moved back to 2.6.34 and the problems disappeared. I'd sooner be one version back and stable, than bleeding edge and constantly falling over. Regards, -- Stuart Longland (aka Redhatter, VK4MSL) .'''. Gentoo Linux/MIPS Cobalt and Docs Developer '.'` : . . . . . . . . . . . . . . . . . . . . . . .'.' http://dev.gentoo.org/~redhatter :.' I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: [gentoo-dev] Restabilizing MIPS
On Thu, Nov 11, 2010 at 06:00:00PM -0500, Matt Turner wrote: > I'd like to begin stabilizing packages on MIPS. I've gotten acks from > Redhatter, leio, and r0bertz, and Kumba doesn't really care. Out of interest, what MIPS hardware do you have? -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpgIabPcmMbT.pgp Description: PGP signature
[gentoo-dev] Restabilizing MIPS
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? Thanks, and any advice is appreciated. :) Matt
