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 1SOzMx-0003z0-9d for garchives@archives.gentoo.org; Mon, 30 Apr 2012 22:47:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E7C54E0B76; Mon, 30 Apr 2012 22:46:50 +0000 (UTC) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) by pigeon.gentoo.org (Postfix) with ESMTP id 86421E0B76 for ; Mon, 30 Apr 2012 22:46:50 +0000 (UTC) Received: by wibhm17 with SMTP id hm17so2783089wib.4 for ; Mon, 30 Apr 2012 15:46:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; bh=fSKNZBPMu9DIA03mjUQbrLzv3XPdcBIAHX8cBGpahfA=; b=jcoKCdB7Xir1hJuXrBZ7AebNM3cC38FNptt3Y4xUQi1TDIc4prwWTfE86Yri38eku+ oOkWwTV2Z/XcQwsi6XR57DL3iB4mp12pODRcZjWTsJRV4FyCt/j+uRqaaOtfn/7Pz8mf oWJa9forBKT4vVKjn96Qhn75KQL1LN0Hv/lRVw1P01Zl76pqLrPjR5wLTP/hd4NpXwBQ Ifo1yr0OqIEtnwoQ/VaEPd5LWs6VR6OmJ76nKaORUmLfSV464fWEqxaIP0DUj0D0Fs8x 6wAiYaASEs7vzehcbzh/3Tjg2ISyGZM5SjmsuCKGtL/Qz8r+tfCguFPqN+0/IFzPvpMK CUlQ== Received: by 10.180.104.230 with SMTP id gh6mr116822wib.22.1335826009668; Mon, 30 Apr 2012 15:46:49 -0700 (PDT) Received: from localhost (cpc13-broo7-2-0-cust130.14-2.cable.virginmedia.com. [82.9.16.131]) by mx.google.com with ESMTPS id ca3sm31664735wib.6.2012.04.30.15.46.48 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Apr 2012 15:46:49 -0700 (PDT) Date: Mon, 30 Apr 2012 23:44:20 +0100 From: Ciaran McCreesh To: gentoo-pms@lists.gentoo.org Subject: Re: [gentoo-pms] Re: EAPI 5 Message-ID: <20120430234420.70607954@googlemail.com> In-Reply-To: <201205010040.32421.dilfridge@gentoo.org> References: <20120415021641.1858ffde@gentoo.org> <201205010014.21031.dilfridge@gentoo.org> <20120430231512.74e964a2@googlemail.com> <201205010040.32421.dilfridge@gentoo.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org Reply-To: gentoo-pms@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/8oHrdxNrxwZ.vQa7GNEUEw0"; protocol="application/pgp-signature" X-Archives-Salt: 14f31456-dbe5-430d-b373-d21986b12945 X-Archives-Hash: e8d9354a999ef3fc4318719f18e7c5cb --Sig_/8oHrdxNrxwZ.vQa7GNEUEw0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 1 May 2012 00:40:32 +0200 "Andreas K. Huettel" wrote: > > I'm against this one in a "quick" EAPI, unless you can get a > > reference implementation and extensive testing on possible use > > scenarios done in time. I strongly suspect this will end up having > > the problems that REQUIRED_USE had when it was shoved in at the > > last minute without anyone having properly tried it out... >=20 > I cannot say much myself about the complexity of the reference > implementation, however the concept itself is imho pretty > straightforward and (in particular) not intrusive. Can you enumerate every possible way the files will be used, both in terms of syntax and intended effect? Can you provide assurances that it can't also be (ab)used to do other things not on your list? Can you demonstrate that introducing this in an EAPI won't require upping profile EAPIs, and that users whose package mangler doesn't do EAPI 5 won't run into problems with it? The interaction of the various use related profile things is already very complicated and messy. We still haven't decided what happens when use dependencies become allowed in profiles, and we're keeping profile EAPIs locked below 2 so we don't have to figure it out. --=20 Ciaran McCreesh --Sig_/8oHrdxNrxwZ.vQa7GNEUEw0 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAk+fFccACgkQ96zL6DUtXhEQLQCeKJl+9heR4qkrKsuJqswQpTXj m98AoMsMWYehop1x/JKPrTeKzPJ2aseK =vIbm -----END PGP SIGNATURE----- --Sig_/8oHrdxNrxwZ.vQa7GNEUEw0--