Date: Wed, 2 Sep 2015 14:28:41 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: <src-committers@FreeBSD.org>, <svn-src-all@FreeBSD.org>, <svn-src-head@FreeBSD.org> Subject: Re: svn commit: r284598 - head/share/mk Message-ID: <16776.1441229321@chaos> In-Reply-To: <55E6516F.5000805@FreeBSD.org> References: <201506191456.t5JEuPDU074336@svn.freebsd.org> <55B8268A.5030305@FreeBSD.org> <4974.1438488939@chaos> <55E6516F.5000805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bryan Drewery <bdrewery@FreeBSD.org> wrote: > My concern is that checked in 'local' files should not be changed by > FreeBSD. I should not have to fight conflicts of _my customizations_ > against _FreeBSD customizations (against bmake upstream)_. There is so > much logic in these local.* files, they seem more aptly named > 'freebsd.*' as they seem to be intended to be customizations for > FreeBSD, rather than optional customizations for a developer or other > downstream consumer of FreeBSD. Yes that's true though src.* is what freebsd is using afaik It will take some time - to optimize this, cleanly separating infrastructure from freebsd specifics. It is not unreasonable for some logic to exist in the checked in local.*.mk to serve as examples. FWIW in re-working our internal build to accommodate what is now in FreeBSD, we now have many of the local.*.mk's include a juniper.*.mk to hold our local customizations with minimal risk of conflicts
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16776.1441229321>