public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Getting EAPI 5 *use.stable.mask to work in gx86?
Date: Thu, 13 Dec 2012 21:33:50 +0100	[thread overview]
Message-ID: <201212132133.57417.dilfridge@gentoo.org> (raw)
In-Reply-To: <50C85CB9.9040603@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1496 bytes --]

Am Mittwoch, 12. Dezember 2012, 11:30:17 schrieb Zac Medico:
> > Yes, and having 'stable' and 'unstable' profiles will work just
> > the same. Except for the fact that it will be a bit cleaner, not require
> > EAPI=5 at all and probably make arch testing a bit easier for a few
> > people.
> 
> Sounds good to me.

Except that it completely breaks stabilization procedures, since packages are 
then not only tested with a larger range of useflags, but with an entirely 
different profile. Not such a great idea. 

The whole point of the stable masking was to keep the changes minimal when 
going from a "testing" to a "stable" state - by only restricting the use flag 
choices, and nothing else. This means most of the testing done with ~arch 
packages is still valid and provides meaningful feedback to maintainers and 
arch teams for stabilization.

In general, using a separate set of profiles, however, whill not help you 
enabling the stable mask files, since these will then only be allowed inside 
the new profiles. Not in the base profile or in the main profile directory, 
which still follows the old EAPI. In the sense of easy handling, noone will 
probably want to edit 
profiles/highly_unstable/next_version/package.stable.mask. 

<rant>I have basically given up that this "feature" will ever become useful 
for the main tree. Long live inertia.</rant>

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-12-13 20:34 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 [this message]
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
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=201212132133.57417.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@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