Date: Fri, 12 Sep 2025 14:59:35 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Kevin Bowling <kevin.bowling@kev009.com> Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: dd8c666d8b78 - main - src.sys.mk: Support src.conf in SRCTOP Message-ID: <86ikhnhlmw.fsf@ltc.des.dev> In-Reply-To: <CAK7dMtA9fjiT8xAgaQFNRzLnqHun=Aq-HZYaEKhWiCRy--Gq%2Bw@mail.gmail.com> (Kevin Bowling's message of "Fri, 12 Sep 2025 03:06:29 -0700") References: <202509101658.58AGwlFE061466@gitrepo.freebsd.org> <CAK7dMtA9fjiT8xAgaQFNRzLnqHun=Aq-HZYaEKhWiCRy--Gq%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Bowling <kevin.bowling@kev009.com> writes: > This turned out to be surprising and led to a puzzle and potentially > unbootable system. I had a very bare bones src.conf in the root from > a long time ago for MIPS hacking, and it got used as my src.conf after > this commit instead of /etc/src.conf. > > I think the order should probably be inverted for POLA, keeping > /etc/src.conf as the primary. That would render the change meaningless. The point is to prefer a local src.conf, if one exists, over a global one. This is particularly useful on development machines, including FreeBSD's own cluster, where multiple source trees exist and regularly get built. In hindsight, I should probably have included an UPDATING entry. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ikhnhlmw.fsf>