From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AD52E1381FB for ; Thu, 27 Dec 2012 21:02:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4128621C2A2 for ; Thu, 27 Dec 2012 21:02:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 34E95E0772 for ; Thu, 27 Dec 2012 20:52:41 +0000 (UTC) Received: from pomiocik.lan (77-255-23-137.adsl.inetia.pl [77.255.23.137]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 19AFE33D8AA; Thu, 27 Dec 2012 20:52:38 +0000 (UTC) Date: Thu, 27 Dec 2012 21:52:41 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-project@lists.gentoo.org Cc: dilfridge@gentoo.org Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08 Message-ID: <20121227215241.631738d8@pomiocik.lan> In-Reply-To: <7346529.VRfjGMRmYK@porto> References: <1356540147.20663.14.camel@localhost> <20121227143738.4d5ce2dd@pomiocik.lan> <7346529.VRfjGMRmYK@porto> Organization: Gentoo X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/V.Kl_QNFaC=psLTz21CYHEA"; protocol="application/pgp-signature" X-Archives-Salt: 91ddd97b-c2a7-423b-9b9d-b57d3e5fbe64 X-Archives-Hash: 651115b8cb95b8d56535c9252b2de2a4 --Sig_/V.Kl_QNFaC=psLTz21CYHEA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 27 Dec 2012 16:21:13 +0100 "Andreas K. Huettel" wrote: > Am Donnerstag, 27. Dezember 2012, 14:37:37 schrieb Micha=C5=82 G=C3=B3rny: > >=20 > > a) adding new profiles which will require EAPI=3D5 and requiring all > > users to migrate to them after upgrading portage. Using new > > use.stable.mask files in those profiles. > >=20 > > 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. > >=20 > > 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. > >=20 >=20 > As the original proponent of the .stable.mask files, I'd recommend soluti= on=20 > c). This is what I intended to achieve in the beginning; I accepted to pl= ace=20 > this into a new profile EAPI after I saw no chance of it going into PMS=20 > otherwise.=20 >=20 > According to PMS, profile directories may contain files not recognized by= the=20 > package manager. A package manager that does not understand the stable.ma= sk=20 > 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=20 > to use the stable.mask files in the main profile directory or the base pr= ofile=20 > (since there the main profile EAPI setting will apply also in the future)= .=20 > Other disadvantages have also been discussed. Yes, especially b) would mostly mean that the *stable.mask files are useful mostly for overlays. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/V.Kl_QNFaC=psLTz21CYHEA Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlDctR0ACgkQfXuS5UK5QB1BTQP/eAhhjaTa3D7fZ1S9eLCYMJFj ECzmfFJSU+jdGl3P3E1/snN5B38ayE+nLak4bS1ofVwwRZtng29HWl1hT0MpL7BO EbAj4xB7fakO7O/86vpPDDANbXflYysuQMDBa72qRRNTX/KbuDxtj+RwnRjWs3ty TWTnNFHHtF3fhbpRNJo= =+h3g -----END PGP SIGNATURE----- --Sig_/V.Kl_QNFaC=psLTz21CYHEA--