Date: Tue, 6 Oct 2015 12:50:40 -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: <15356.1444161040@chaos> In-Reply-To: <56140CAD.8080200@FreeBSD.org> References: <201510060418.t964Innu071170@repo.freebsd.org> <56140CAD.8080200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bryan Drewery <bdrewery@freebsd.org> wrote: > Why would anyone build ports in a sub-dir of src? It's convenient for a > vendor building their own product that needs their own ports tree. Some > decisions can't easily be changed; if the root of the source code > checkout is already src/, there is no simple way to avoid the problem. 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15356.1444161040>