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 1NwveJ-0006dY-BL for garchives@archives.gentoo.org; Wed, 31 Mar 2010 10:59:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0CC49E0C13; Wed, 31 Mar 2010 10:59:49 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 12A73E0B9E; Wed, 31 Mar 2010 10:59:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 8327D1B4058; Wed, 31 Mar 2010 10:59:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.088 X-Spam-Level: X-Spam-Status: No, score=-2.088 required=5.5 tests=[AWL=0.511, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JK2UmQ43JwVf; Wed, 31 Mar 2010 10:59:33 +0000 (UTC) Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by smtp.gentoo.org (Postfix) with ESMTP id EEA9B1B403A; Wed, 31 Mar 2010 10:59:32 +0000 (UTC) Received: by pzk5 with SMTP id 5so707283pzk.0 for ; Wed, 31 Mar 2010 03:59:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=SyA2j8UG40JNbEWwlC0+ZPsCjCFVE9L14TbRjVuAPPY=; b=ANJj+NGC/uNy339ZdRxllOSmzCtQ/bdoTrRP0uLQpGJ1TzPkGxKOnddkvB4CCPRI5m rjxM8ZRKgYQMF2QDSBBzmNYG3Kt6tKfAAE+CisB6actKMwAzS5AQfI8F2cs1WY5A9K86 K2DuA5to6No6NIxDiyVi+fgU6MijMH5tEcHr8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=wJ6op8R8+zMoTwf4fJEJTlSUa/u4LtYpUDwqSrN7NBM7KlEy5KW5H2Inpm5ok8ijqS PwYGHUASmYeBApuQeLYNvtE1dZytKCwEHVSNRWQRQnDJS9+iJ/ie+colQzZhKoe/oeWi i+HEHR9xywPN9Alodtc9gS/+cC4rZCZWzdQp0= Received: by 10.143.153.42 with SMTP id f42mr85346wfo.299.1270033172217; Wed, 31 Mar 2010 03:59:32 -0700 (PDT) Received: from smtp.gmail.com (c-67-171-128-62.hsd1.wa.comcast.net [67.171.128.62]) by mx.google.com with ESMTPS id 23sm5856132pzk.6.2010.03.31.03.59.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 03:59:31 -0700 (PDT) Received: by smtp.gmail.com (sSMTP sendmail emulation); Wed, 31 Mar 2010 03:57:38 -0700 Date: Wed, 31 Mar 2010 03:57:38 -0700 From: Brian Harring To: Alistair Bush Cc: gentoo-dev@lists.gentoo.org, gentoo-council@lists.gentoo.org Subject: [gentoo-dev] Re: [gentoo-council] pkg_pretend USE validation and VALID_USE alternative Message-ID: <20100331105738.GE11663@hrair> References: <20100331092035.GA11663@hrair> <201003312316.23806.ali_bush@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VUDLurXRWRKrGuMn" Content-Disposition: inline In-Reply-To: <201003312316.23806.ali_bush@gentoo.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: bcd6a505-14cd-4eb3-b708-75cc0667319e X-Archives-Hash: b9b709041dcdce7901a3d80498a11286 --VUDLurXRWRKrGuMn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Note I inadvertantly cross posted, I was intending on cc'ing=20 council@gentoo.org. As such one final cc to that ml to end this subthread while pulling=20 this back to -dev. On Wed, Mar 31, 2010 at 11:16:22PM +1300, Alistair Bush wrote: > > Hola all- > > =20 > > Comments desired; assuming no significant blowback, I'll be pushing > > this to the council level since eapi4 is annoying feature locked right >=20 > I think this solution is far better, until someone smarter than me tells= me=20 > otherwise. >=20 > Don't know whether I like the VALID_USE var name, so please at least thi= nk=20 > about something a little better if you can ;). ( I like green, but not = too=20 > green if you know what I mean ) > > Will we still have to define the use flags in IUSE? Yes, although if folks have a better proposal that incorporates=20 VALID_USE into IUSE I'm definitely open to it- the original proposal=20 for VALID_USE tried to inline it into IUSE, but it got ugly (hence it=20 mutating it this form). The problem w/ trying to reuse IUSE is the following (sorry, I like=20 lists of assertions)- *) IUSE currently serves as a list of valid USE flags, just that. No=20 repeat specification of a flag (which means the dev in question is=20 unlikely to typo a flag). *) having a single specified list of valid use flags is the basis for=20 doing validation of use flags used in all other metadata. In other=20 words, that list of valid use flags *really* needs to go out of it's=20 way to make human error hard. *) VALID_USE is a set of assertions on the allowed state of USE; IUSE=20 is just a list of flags. Intermixing the two in a way that is still=20 readable is really ugly *) given a library that has optional perl and python bindings=20 (which can be toggled freely, they're standalone flags) I've nfc how=20 one would sanely specify that w/in IUSE while adding VALID_USE=20 semantics. Possibly, you could include use conditionals into IUSE,=20 and treat the () contents as assertions- but that makes adding xor in=20 hard, is rather ugly/hard on the eyes, and violates the DRY (Don't=20 Repeat Yourself) principle from above. Definitely open to counterproposals that address those=20 concerns however... > I'm guessing we can't use IUSE to store this information because of the = whole=20 > glep-55 thing. glep-55 is unrelated to this as far as I can tell- if you think=20 otherwise please clarify. Thanks ~harring --VUDLurXRWRKrGuMn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) iEYEARECAAYFAkuzKqIACgkQsiLx3HvNzgdgLgCfV7miXsGHC2LIXkbITZzImC5q iiYAnijRS7iSEt0mAMAxy19W4QKoI7dw =fjd1 -----END PGP SIGNATURE----- --VUDLurXRWRKrGuMn--