From owner-freebsd-current@freebsd.org Sat Nov 5 23:33:02 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83383C30114 for ; Sat, 5 Nov 2016 23:33:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-55.reflexion.net [208.70.210.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3136631A for ; Sat, 5 Nov 2016 23:33:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 8818 invoked from network); 5 Nov 2016 23:32:50 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 5 Nov 2016 23:32:50 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.10.1) with SMTP; Sat, 05 Nov 2016 19:33:04 -0400 (EDT) Received: (qmail 7706 invoked from network); 5 Nov 2016 23:33:04 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 Nov 2016 23:33:04 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 614AAEC8BDB; Sat, 5 Nov 2016 16:32:54 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: Use of env SRC_ENV_CONF=. . . for buildworld does not override/avoid use of /etc/src.conf : Intentional? From: Mark Millard In-Reply-To: Date: Sat, 5 Nov 2016 16:32:53 -0700 Cc: FreeBSD Toolchain , FreeBSD-STABLE Mailing List , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <12E108A2-21FE-4756-B099-334ADD020891@dsl-only.net> To: Bryan Drewery X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2016 23:33:02 -0000 On 2016-Nov-4, at 9:40 AM, Bryan Drewery = wrote: > On 11/3/2016 5:28 PM, Mark Millard wrote: >> I just had a case of "odd" command text in a buildworld that was = based on (in part) env SRC_ENV_CONF=3D. . . >>=20 >> env __MAKE_CONF=3D. . . does not get the kind of behavior reported = below for /etc/src.conf . >>=20 >> Overall this means that even with an explicit env SRC_ENV_CONF=3D. . = . one must separately prevent /etc/src.conf from contributing if the = SRC_ENV_CONF file is intended to cover everything. >=20 > SRC_ENV_CONF is kind of a special hack to allow setting some specific > values that feasibly can't be set later. Just stick to src.conf = unless > you need to set one of the options that requires src-env.conf. >=20 > --=20 > Regards, > Bryan Drewery Understood (now): intentional for sure. Thanks to Renato Botelho and you = for making clear that I'd read something into the description that just was = not written into the description. For now I've adopted using an explicit env SRCCONF=3D"/dev/null" in the = scripts as the means of avoiding an unexpected contribution and I still have env = SRC_ENV_CONF=3D use for picking out the file: I then do not have to worry about if I = reference any of the special values in the file referenced or not, nor about what /etc/src-env.conf or /etc/src.conf might have in them. I may change this at some point and follow your suggestion to just use = SRCCONF=3D to find the file because as time goes on it looks more like I'm unlikely = to experiment with any "special values" in the files. =3D=3D=3D Mark Millard markmi at dsl-only.net