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 1Lgn1X-0002To-HV for garchives@archives.gentoo.org; Mon, 09 Mar 2009 21:28:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 799EFE03F4; Mon, 9 Mar 2009 21:28:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 52C72E03F4 for ; Mon, 9 Mar 2009 21:28:34 +0000 (UTC) Received: from [192.168.22.10] (ip68-4-152-120.oc.oc.cox.net [68.4.152.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id D4ECB647F9 for ; Mon, 9 Mar 2009 21:28:33 +0000 (UTC) Message-ID: <49B58A10.5080903@gentoo.org> Date: Mon, 09 Mar 2009 14:28:48 -0700 From: Zac Medico User-Agent: Thunderbird 2.0.0.19 (X11/20081209) 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] Ideas for a (fast) EAPI=3 References: <1236498557.6854.51.camel@neuromancer> <20090309202624.723e4b2a@snowcone> <49B58273.3000401@gentoo.org> <20090309210819.0a84e180@snowmobile> In-Reply-To: <20090309210819.0a84e180@snowmobile> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 0e2b0ccb-f56d-4144-a76e-aba3d1a12aef X-Archives-Hash: 012aee0c55c8f719bcd11dc6df05b0f0 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Mon, 09 Mar 2009 13:56:19 -0700 > Zac Medico wrote: >> Ciaran McCreesh wrote: >>> * Limit values in $USE to ones in $IUSE (bug 176467). The existing >>> behaviour's majorly annoying; time for the package manager to >>> start enforcing things strictly. >> My impression is that most ebuild developers tend to dislike the >> idea of adding profile-specific flags such as $ARCH, userland_*, >> kernel_*, and elibc_* to IUSE. Perhaps there should be exemptions >> for these? > > If we must do that... Can we get something in profiles a bit like this: > > USE_EXPAND_IMPLICIT="USERLAND KERNEL ELIBC ARCH" > USE_EXPAND_UNPREFIXED="ARCH" > USE_EXPAND_VALUES_USERLAND="GNU freebsd" > USE_EXPAND_VALUES_KERNEL="linux blah" > USE_EXPAND_VALUES_ELIBC="glibc" > USE_EXPAND_VALUES_ARCH="x86 amd64 sparc mips blah" > > so we've got an enforcable complete list of every legal value for > them, and less associated mess? That seems like a reasonable approach. What about flags that are commonly forced or masked such as selinux or multilib? Should there be an implicit exemption for all forced/masked flags, or should we introduce an IMPLICIT_IUSE profile variable to enumerate specific ones which are implicit members of IUSE? - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEARECAAYFAkm1ig8ACgkQ/ejvha5XGaMpxwCgqi0Ma+Wv9s0coMYtagWR8Je/ hBEAn3awatpk505DxKrGtYDwTSYgn+nZ =XHzp -----END PGP SIGNATURE-----