From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F37521389E2 for ; Mon, 29 Dec 2014 03:01:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0E8EDE09B2; Mon, 29 Dec 2014 03:01:51 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7E8F4E09A4 for ; Mon, 29 Dec 2014 03:01:50 +0000 (UTC) Received: from [192.168.1.4] (ip70-181-96-121.oc.oc.cox.net [70.181.96.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 6B36A3405BB for ; Mon, 29 Dec 2014 03:01:49 +0000 (UTC) Message-ID: <54A0C41B.7020605@gentoo.org> Date: Sun, 28 Dec 2014 19:01:47 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Re: [PATCH] man pages: note that make.conf can be a directory (463266) References: <1419631307-30949-1-git-send-email-zmedico@gentoo.org> <549E573A.3090104@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: fdc3e7d6-f039-4d11-8d11-691e98f59a9f X-Archives-Hash: e4483fd74b524ae669731496e7457354 On 12/28/2014 06:55 PM, Duncan wrote: > Zac Medico posted on Fri, 26 Dec 2014 22:52:42 -0800 as excerpted: > >>> I believe that's why I chose to stick with a make.conf file that simply >>> sourced a bunch of other files, instead of simply making it a directory >>> and sticking all those other files in the dir, when I first read about >>> the possibility. I have scripts myself that simply source make.conf, >>> that I'd have to rewrite with a for loop to process a directory. It's >>> not hard to do, but people haven't had to worry about it and so they >>> haven't. If people aren't thinking about that when they up and make >>> make.conf a directory, they might well wish they had! =8^0 >> >> Why don't you use 'portageq envvar'? > > Thanks for the hint. I will likely use it. =:^) > > Which hints at half the answer to your question; I didn't really know > about it. The other half of the answer is simple. It was never needed > before, as sourcing make.conf always "just worked". Now that it's > needed... Thanks again! =:^) Note that it's handy to pull multiple variables into your environment with a single portageq call like this: eval "$(portage envvar -v VARIABLE_1 VARIABLE_2 ...)" For example, we use this construct in emerge-webrsync. -- Thanks, Zac