[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-mips
Subject:    Re: [gentoo-mips] Restore stable keywords on @system
From:       Markos Chandras <hwoarang () gentoo ! org>
Date:       2014-01-23 20:48:39
Message-ID: 52E18027.7050401 () gentoo ! org
[Download RAW message or body]

On 01/22/2014 09:01 PM, Matt Turner wrote:
> On Wed, Jan 22, 2014 at 12:42 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
>> https://bugs.gentoo.org/show_bug.cgi?id=498818 debates the need to
>> restore the stable keywords to the @system packages in order to ease
>> the build of stage3 tarballs. Right now there is a little bit of
>> hackery (read masking) when we build the tarballs since not all the
>> latest packages build on MIPS. However, in my opinion, restoring the
>> stable keywords on MIPS add extra maintenance effort to an already
>> understaffed team by requiring us to test both the latest ~arch and
>> the latest stable of all the packages in the @system set.
> 
> I've definitely experienced ~arch problems when building stages. Now
> that you and Anthony have taken over those tasks, I don't think my
> opinion about which is easier (stable @system, or masking versions
> during stage building) is relevant.
I am building mips64r2 as we speak, and I have no problems at the moment.

The usual blockers were python-3 with multilib stuff blah blah
(python-3.3 works ok) and texinfo from
https://bugs.gentoo.org/show_bug.cgi?id=471192

both seem to be resolved at this point.

> 
> I think that you're probably right about the added problems of
> attempting to keep a stable @system. Other stable architecture teams
> aren't really able to keep up and I'm not convinced that we should
> try.

Given the limited manpower and hardware we have, I would say it is very
hard to dedicate a box for testing a stable @system. If someone wants to
take over this role, then fine by me, but we need to make sure he will
be around and do this for as long as it takes.

Personally, I am happy the way things are at the moment and fixing
~arch should be our priority

-- 
Regards,
Markos Chandras

[prev in list] [next in list] [prev in thread] [next in thread]