public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hwoarang@gentoo.org
Subject: Re: [gentoo-dev] Getting EAPI 5 *use.stable.mask to work in gx86?
Date: Fri, 14 Dec 2012 16:15:05 +0100	[thread overview]
Message-ID: <20121214161505.56c76c91@pomiocik.lan> (raw)
In-Reply-To: <CAG2jQ8iUWtUBv4f1h2dRUWSeiGn4T4e_FVJt5pTkOsTRPKTHhA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]

On Fri, 14 Dec 2012 15:08:24 +0000
Markos Chandras <hwoarang@gentoo.org> wrote:

> On 14 December 2012 14:59, Michał Górny <mgorny@gentoo.org> wrote:
> >
> >> We already have plenty of understaffed arches, I don't think it is
> >> wise to throw more responsibilities to them. Unless of course all
> >> developers are allowed to touch these *stable* profiles which
> >> personally I don't like because arches will lose
> >> control of their stable trees.
> >
> > I'd like to point out that my proposal implies that the *current*
> > arches become the stable arches, and new sub-arches would be
> > the testing ones. Therefore, everyone will be allowed to touch like
> > everyone is allowed to touch the *stable* profiles today.
> >
> > In other words, we mask python_targets_pypy* in the base profiles,
> > and unmask them in the testing sub-profiles for amd64 & x86.
> >
> > --
> > Best regards,
> > Michał Górny
> 
> I fear that the stable and testing profiles will diverge way too much
> as time passes. But if you feel that maintainers and
> herds will be able to keep the 'diff' between them as minimum as
> possible, then I have no objections.

Well, my hope is that we will be able to do it mostly via a common
'testing' profile (or per-arch testing profiles) which will be parents
to other sub-profiles. 

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-12-14 15:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 21:27 [gentoo-dev] Getting EAPI 5 *use.stable.mask to work in gx86? Michał Górny
2012-12-11  2:01 ` Ian Stakenvicius
2012-12-11  6:32   ` Michał Górny
2012-12-11  6:35 ` Zac Medico
2012-12-11 21:45   ` Michał Górny
2012-12-12  0:44     ` Zac Medico
2012-12-12  9:32       ` Michał Górny
2012-12-12 10:30         ` Zac Medico
2012-12-13 20:33           ` Andreas K. Huettel
2012-12-13 20:43             ` Michał Górny
2012-12-13 21:46               ` Zac Medico
2012-12-14 12:38                 ` Markos Chandras
2012-12-14 14:29                   ` Michał Górny
2012-12-14 14:36                     ` Markos Chandras
2012-12-14 14:39                       ` Ian Stakenvicius
2012-12-14 15:00                         ` Michał Górny
2012-12-14 14:59                       ` Michał Górny
2012-12-14 15:08                         ` Markos Chandras
2012-12-14 15:15                           ` Michał Górny [this message]
2012-12-14 20:50                             ` [gentoo-dev] " Duncan

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=20121214161505.56c76c91@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hwoarang@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