public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: chainsaw@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08
Date: Thu, 27 Dec 2012 14:37:37 +0100	[thread overview]
Message-ID: <20121227143738.4d5ce2dd@pomiocik.lan> (raw)
In-Reply-To: <1356540147.20663.14.camel@localhost>

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

On Wed, 26 Dec 2012 16:42:27 +0000
"Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org> wrote:

> In less than two weeks, on Tuesday January the 8th, the council will meet again. 
> Now is the time to prepare & raise items that you feel should be put to a vote.
> 
> Please reply to this e-mail with any suggested agenda items. Even if you have raised 
> the issue on a mailing list before, please repeat it now to avoid it being missed.

I'd like the Council to raise the topic of using stable USE masks
in gx86 tree.

The issue is that Python packages have USE-conditional (PYTHON_TARGETS)
dependencies upon new, unstable Python versions. Therefore,
if a particular package is to be stabilized, the relevant USE flags have
to be masked (or removed) in order to fulfill the dependencies
on a stable system.

Currently we're resolving this through using two revisions
for a package, one with the relevant flags removed (going stable)
and a newer one with all flags enabled. However, this is very
inconvenient for us.

EAPI 5 provides use.stable.mask files to solve this but those files
require profiles to be EAPI 5. Therefore, in order to be able to use it
we would have to actually break the update path for older portage
versions completely.

I have tried to raise the topic on the mailing list [1] but it mostly
resulted in some people agreeing that it is an issue that should be
addressed but no real ideas.

I have come up with three possible solutions myself. Long story short:

a) adding new profiles which will require EAPI=5 and requiring all
users to migrate to them after upgrading portage. Using new
use.stable.mask files in those profiles.

b) adding new profiles (with current EAPIs) and requesting our unstable
users to migrate to them. Masking the relevant USE flags globally
and unmasking in those profiles.

c) 'fixing' the use.stable.mask feature and wording it in such a way
that it would apply to EAPI 5 (or 6) packages independently of profiles
EAPI.

I have also opened bug 447090 [2] in order to try to get some feedback
on b) but nobody bothered to answer.

[1]:http://thread.gmane.org/gmane.linux.gentoo.devel/81877
[2]:https://bugs.gentoo.org/show_bug.cgi?id=447090

-- 
Best regards,
Michał Górny

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

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 16:42 [gentoo-project] Call for agenda items -- Council meeting 2013-01-08 Tony "Chainsaw" Vroon
2012-12-27 13:37 ` Michał Górny [this message]
2012-12-27 15:21   ` Andreas K. Huettel
2012-12-27 20:52     ` Michał Górny
2012-12-27 19:56   ` Ciaran McCreesh
2012-12-27 20:54     ` Michał Górny
2012-12-27 20:41   ` Zac Medico
2012-12-27 20:55     ` Michał Górny
2013-02-05 22:03 ` [gentoo-project] Preliminary agenda -- Council meeting 2013-02-12 Tony "Chainsaw" Vroon

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=20121227143738.4d5ce2dd@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=chainsaw@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@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