From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MmcmP-0003GN-Pl for garchives@archives.gentoo.org; Sun, 13 Sep 2009 00:17:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8785CE081D; Sun, 13 Sep 2009 00:17:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 690A0E081D for ; Sun, 13 Sep 2009 00:17:20 +0000 (UTC) Received: from [192.168.1.15] (bl9-45-81.dsl.telepac.pt [85.242.45.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 937B36446F for ; Sun, 13 Sep 2009 00:17:19 +0000 (UTC) Message-ID: <4AAC39FB.2000808@gentoo.org> Date: Sun, 13 Sep 2009 00:16:59 +0000 From: "Jorge Manuel B. S. Vicetto" User-Agent: Thunderbird 2.0.0.23 (X11/20090830) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 To: gentoo-council@lists.gentoo.org Subject: Re: [gentoo-council] Agenda for September 14th meeting References: <1252757649.6044.5.camel@homer.ob.libexec.de> <20090912160801.2d679976@snowcone> <4AAC352A.50008@gentoo.org> <20090913010503.0ad46402@snowmobile> In-Reply-To: <20090913010503.0ad46402@snowmobile> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d927caa3-73cb-41da-b3ef-3568c346920f X-Archives-Hash: b6182724ce090dd901bb51020cebbc7b -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Sat, 12 Sep 2009 23:56:26 +0000 "Jorge Manuel B. S. Vicetto" > wrote: >> it isn't a "mistaken impression". Both Joshua and me think there >> are alternatives and that the choice to put profiles/* under EAPI >> was unfortunate and should be reviewed. > > Why were those alternatives never expressed? Why were your > objections not raised at the time, and why have you never explained > what you think is wrong with it or what you think a better option > would be? > Because at the time we didn't thought about them, didn't had time to follow the infinite discussions about EAPI, just plain didn't cared about it or some other reason. That's why we would like the council to discuss about alternatives. >> It's also my opinion that what the council approved was the use >> of a EAPI file under each profile to mark the type of atoms that >> can be used in the profile files (slots, etc). > > What the council agreed upon is not a matter of opinion. The > council agreed to introduce EAPI control to profiles/. This was in > no way limited to "the types of atoms that can be used", and the > wording and design were very deliberately constructed *not* to > limit the changes to those kinds of things. > I'd have to check the exact wording as I never followed EAPI discussions that closely - you have. However, I'm pretty sure that everything I saw leading up to the discussion addressed the concern of using new atom syntaxes in files under profiles (in particular package.mask/package.keywords/package.use files) and I do recall the discussion about profiles/ itself having to be restricted to EAPI-0 which meant that we couldn't use newer syntax (in particular slots) for the global package.mask. I don't recall any discussion regarding other use of EAPI in profiles - at that time. - -- Regards, Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo- forums / Userrel / Devrel / SPARC / KDE -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqsOfsACgkQcAWygvVEyAKxJACeJSVu/aoKr5EER7lpubWYM82C kgQAn2hX2yI79cHwpnDV1z6f3lEP3EDT =JlzE -----END PGP SIGNATURE-----