Date: Tue, 6 Oct 2015 14:17:03 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: Warner Losh <imp@FreeBSD.org>, <src-committers@FreeBSD.org>, <svn-src-all@FreeBSD.org>, <svn-src-head@FreeBSD.org>, <sjg@juniper.net> Subject: Re: svn commit: r288911 - head/share/mk Message-ID: <18968.1444166223@chaos> In-Reply-To: <5614286D.7020904@FreeBSD.org> References: <201510060418.t964Innu071170@repo.freebsd.org> <56140CAD.8080200@FreeBSD.org> <15356.1444161040@chaos> <5614286D.7020904@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bryan Drewery <bdrewery@FreeBSD.org> wrote: > > But wouldn't that imply that /usr/src/share/mk is the right set of > > makefiles to use for /usr/src/ports/ > > > > What would you consider the right sys.mk etc would be in such a case? > > > > For our case we want the checked in src/share/mk to be used rather than Are you refering to a src/share/mk which is sibling to src/ports/* or something else? Because with MAKESYSPATH=.../share/mk src/share/mk/sys.mk is what you should find. > the older /usr/share/mk as it is easier to support. If there's a problem > we fix in our local.sys.env.mk or bsd.port.mk for instance, it will be > used by updating the checkout. This was something we backported, > without the src.conf inclusion in sys.mk, and were running with fine. I might be confused... It might help to differentiate the question of finding the right sys.mk which IMO is critical to a happy outcome, from what to do with src.* if present. Normally anything under $SRCTOP should be subject to src.* - by definition. But there's no reason you cannot make exceptions - by (as I think you already mentioned) adding a check for $SRCTOP/ports in local*sys*mk to suppress src.conf at least.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18968.1444166223>