From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1FydOh-00079W-5w for garchives@archives.gentoo.org; Thu, 06 Jul 2006 23:36:39 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k66NXQbR003465; Thu, 6 Jul 2006 23:33:26 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k66NRwt7026133 for ; Thu, 6 Jul 2006 23:27:59 GMT Received: from [192.168.24.6] (ip68-5-234-231.oc.oc.cox.net [68.5.234.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 595036443C for ; Thu, 6 Jul 2006 23:27:58 +0000 (UTC) Message-ID: <44AD9C6B.5030704@gentoo.org> Date: Thu, 06 Jul 2006 16:27:39 -0700 From: Zac Medico User-Agent: Thunderbird 1.5.0.4 (X11/20060603) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] USE_EXPAND_HIDDEN: why make.globals? References: <20060706223328.47e1a4f2@snowdrop.home> In-Reply-To: <20060706223328.47e1a4f2@snowdrop.home> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 5841d2e3-531f-4a91-8a27-a564ec468a5e X-Archives-Hash: 5526a6f3df616caceb914815e37a067e -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > Is there any particular reason USE_EXPAND_HIDDEN needs to be in > make.globals, as opposed to in base/make.defaults alongside USE_EXPAND? > Seems to me it'd make more sense were the two kept together... Given the support that's currently available in portage, that seems like a good move to my. However, I've been thinking about proposing the addition of support for things like $PORTDIR/profiles/{make.defaults,bashrc,package.use} as part of a "repo level" profile. These would be a logical extension of the support that already exists for $PORTDIR/profiles/package.mask. But anyway, base/make.defaults makes sense for now. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFErZxp/ejvha5XGaMRAvw4AKCiNolBORuKxOhptk6THRqG8PrmkwCgwCVt hjybF1i7x/ymSkKx7QbxyEg= =kziC -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list