public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08
Date: Thu, 27 Dec 2012 16:22:46 +0100	[thread overview]
Message-ID: <3824174.B5SVJmv9QO@porto> (raw)
In-Reply-To: <20121227143738.4d5ce2dd@pomiocik.lan>

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

Am Donnerstag, 27. Dezember 2012, 14:37:37 schrieb Michał Górny:
> 
> 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.
> 

As the original proponent of the .stable.mask files, I'd recommend solution 
c). This is what I intended to achieve in the beginning; I accepted to place 
this into a new profile EAPI after I saw no chance of it going into PMS 
otherwise. 

According to PMS, profile directories may contain files not recognized by the 
package manager. A package manager that does not understand the stable.mask 
files will thus -if PMS-compliant- just ignore them.

Solutions a) and b) have the big disadvantage that you will never ever be able 
to use the stable.mask files in the main profile directory or the base profile 
(since there the main profile EAPI setting will apply also in the future). 
Other disadvantages have also been discussed.

-- 
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: 836 bytes --]

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 16:42 [gentoo-dev] Call for agenda items -- Council meeting 2013-01-08 Tony "Chainsaw" Vroon
2012-12-27 13:37 ` [gentoo-dev] Re: [gentoo-project] " Michał Górny
2012-12-27 15:22   ` Andreas K. Huettel [this message]
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
2012-12-27 23:40   ` Andreas K. Huettel
2012-12-28  1:59     ` Zac Medico
2012-12-28 10:19     ` Michał Górny
2012-12-28 18:06       ` Andreas K. Huettel
2012-12-28 19:03         ` Michał Górny
2012-12-28 19:24           ` Andreas K. Huettel
2012-12-28 19:29             ` [gentoo-dev] Bad GPG key Alexander Berntsen
2012-12-28 19:30               ` Alexander Berntsen
2012-12-28 19:40               ` Andreas K. Huettel
2012-12-29  3:05     ` [gentoo-dev] Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08 Ben Kohler
2012-12-29  9:39       ` Tony "Chainsaw" Vroon
2013-02-05 22:03 ` [gentoo-dev] 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=3824174.B5SVJmv9QO@porto \
    --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