From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KPRmM-0003rD-P2 for garchives@archives.gentoo.org; Sun, 03 Aug 2008 00:48:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DBD2DE0146; Sun, 3 Aug 2008 00:48:56 +0000 (UTC) Received: from 10ibp20ser03.datacenter.cha.cantv.net (10ibp20ser03.datacenter.cha.cantv.net [200.11.173.14]) by pigeon.gentoo.org (Postfix) with ESMTP id A2128E0146 for ; Sun, 3 Aug 2008 00:48:56 +0000 (UTC) X-DNSBL-MILTER: Passed Received: from localhost (dbe25bf45.dslam-172-17-161-239-0073-262.dsl.cantv.net [190.37.191.69] (may be forged)) by 10ibp20ser03.datacenter.cha.cantv.net (8.14.3/8.14.3/3.0) with ESMTP id m730mqxZ001658 for ; Sat, 2 Aug 2008 20:18:55 -0430 X-Matched-Lists: [] Received: from localhost ([127.0.0.1]) by localhost with esmtp (Exim 4.69) (envelope-from ) id 1KPR4q-0001fD-2F for gentoo-dev@lists.gentoo.org; Sat, 02 Aug 2008 20:04:00 -0400 Message-ID: <4894F5EF.7040200@gentoo.org> Date: Sat, 02 Aug 2008 20:03:59 -0400 From: Luis Francisco Araujo User-Agent: Thunderbird 2.0.0.14 (X11/20080521) 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds? References: <4893C048.9020806@gentoo.org> <48942485.4000808@gentoo.org> <48943642.1080009@gentoo.org> <48944F98.6090002@gentoo.org> <4894E102.6020300@gentoo.org> <4894E8BA.9020904@necoro.eu> <4894EE60.9050008@gentoo.org> <4894F29F.1050802@necoro.eu> In-Reply-To: <4894F29F.1050802@necoro.eu> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed X-SPF-Scan-By: smf-spf v2.0.2 - http://smfs.sf.net/ Received-SPF: Neutral (10ibp20ser03.datacenter.cha.cantv.net: 190.37.191.69 is neither permitted nor denied by domain of araujo@gentoo.org) receiver=10ibp20ser03.datacenter.cha.cantv.net; client-ip=190.37.191.69; envelope-from=; helo=localhost; X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on 10ibp20ser03.datacenter.cha.cantv.net X-Virus-Status: Clean Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 21e7fe47-82ad-4215-8237-61310deed5ca X-Archives-Hash: 4a47d3774347c68170b323b5744508f5 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ren=C3=A9 'Necoro' Neumann wrote: | Zac Medico schrieb: |> Well, RESTRICT has long since evolved into a rather generic set of |> boolean flags and it's quite useful as such. I don't see any need |> for artificial limitations on what types of flags go there. | | For you it is just "one variable amongst others" - and you really don't | care about the relation between its name and its content. But perhaps | just for the sake of easier understanding of ebuilds, this relation | should be kept. Otherwise you'll read in future documentation: "The nam= e | is just for historical reasons and does not reflect the content." -- An= d | this is nearly always a stumbling block for the non-experienced. | | Perhaps in a later EAPI RESTRICT might be renamed to something like | FLAGS - and then can really be used as a pool of flags. Can the RESTRICT=3D"live" value be interpreted as , 'restrict this ebuild to live repositories' or , if you want, 'this package will only build from live repos'? In either case, I don't see the fuss regarding this naming thing, considering RESTRICT is already being used for similar functionality. Regards, - -- Luis F. Araujo "araujo at gentoo.org" Gentoo Linux -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiU9e8ACgkQNir3WYj9aLpH0wCfS0t7t9md+kPmVZsppiekybe4 TNUAoIsGXS+wnGTpqZRNLpRTLwSGG7vk =3DxLIG -----END PGP SIGNATURE-----