public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Restore stable keywords on @system
Date: Wed, 22 Jan 2014 13:01:26 -0800	[thread overview]
Message-ID: <CAEdQ38GvGJDGFgQRVoyb21478Hoc0oyAX1J6fdiY=TYJce3bzw@mail.gmail.com> (raw)
In-Reply-To: <52E02D2D.2070003@gentoo.org>

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 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.

I haven't powered on my MIPS machines since I moved houses in August,
and I'm not likely to come into lots of new free time to help
stabilize things.


  reply	other threads:[~2014-01-22 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 20:42 [gentoo-mips] Restore stable keywords on @system Markos Chandras
2014-01-22 21:01 ` Matt Turner [this message]
2014-01-23 20:48   ` Markos Chandras
2014-02-09  7:48     ` Joshua Kinard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEdQ38GvGJDGFgQRVoyb21478Hoc0oyAX1J6fdiY=TYJce3bzw@mail.gmail.com' \
    --to=mattst88@gentoo.org \
    --cc=gentoo-mips@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox