Date: Sat, 03 Mar 2012 12:12:03 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Ben Kaduk <minimarmot@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Dimitry Andric <dim@freebsd.org> Subject: Re: svn commit: r232473 - in head: share/mk sys/conf Message-ID: <4F527B13.4030607@FreeBSD.org> In-Reply-To: <CAK2BMK4J%2B9zNKARn0HK-v2sTaNT0av7g=s3_nsrCP-Ey7CiecA@mail.gmail.com> References: <201203031858.q23IwGvG096048@svn.freebsd.org> <4F5278F8.2020109@FreeBSD.org> <CAK2BMK4J%2B9zNKARn0HK-v2sTaNT0av7g=s3_nsrCP-Ey7CiecA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 03/03/2012 12:05, Ben Kaduk wrote:
> On Sat, Mar 3, 2012 at 3:03 PM, Doug Barton <dougb@freebsd.org> wrote:
>> On 03/03/2012 10:58, Dimitry Andric wrote:
>>> However, since it is apparently an expected use case to build using old
>>> .mk files,
>>
>> Expected how? It shouldn't happen if you're building in /usr/src.
>> Wouldn't it be better to track down the real bug?
>
> I, for one, am frequently building in /usr/ports. I have not checked,
> but I could very easily see that pulling the system .mk files from the
> installed locations and not the source tree.
Building ports where the sources and the installed kernel differ is not
a supported configuration. The fact that it happens to work most of the
time is a bonus.
This is a very dangerous precedent to set.
--
This .signature sanitized for your protection
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F527B13.4030607>