From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: dilfridge@gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08
Date: Thu, 27 Dec 2012 21:52:41 +0100 [thread overview]
Message-ID: <20121227215241.631738d8@pomiocik.lan> (raw)
In-Reply-To: <7346529.VRfjGMRmYK@porto>
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
On Thu, 27 Dec 2012 16:21:13 +0100
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:
> 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.
But the PMS-compliant package managers would not apply them as well. So
we either have to do that in a new EAPI which could be a bit confusing
in wording, or retroactively change EAPI 5 which will require fixes to
package managers and could cause random issues with stable systems
which haven't updated the pm yet.
> 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.
Yes, especially b) would mostly mean that the *stable.mask files are
useful mostly for overlays.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-12-27 21: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
2012-12-27 15:21 ` Andreas K. Huettel
2012-12-27 20:52 ` Michał Górny [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
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=20121227215241.631738d8@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=dilfridge@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