Date: Thu, 1 Feb 2007 12:40:52 -0800 From: Luigi Rizzo <rizzo@icir.org> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@freebsd.org Subject: Re: /usr/local/share/mk ? Message-ID: <20070201124052.D84181@xorpc.icir.org> In-Reply-To: <20070201202511.GA74029@xor.obsecurity.org>; from kris@obsecurity.org on Thu, Feb 01, 2007 at 03:25:11PM -0500 References: <20070201111727.B83474@xorpc.icir.org> <20070201192051.GA72926@xor.obsecurity.org> <20070201113720.D83474@xorpc.icir.org> <20070201194417.GA73296@xor.obsecurity.org> <20070201122011.B84181@xorpc.icir.org> <20070201202511.GA74029@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 01, 2007 at 03:25:11PM -0500, Kris Kennaway wrote:
> On Thu, Feb 01, 2007 at 12:20:11PM -0800, Luigi Rizzo wrote:
> > On Thu, Feb 01, 2007 at 02:44:17PM -0500, Kris Kennaway wrote:
> > > On Thu, Feb 01, 2007 at 11:37:20AM -0800, Luigi Rizzo wrote:
> > ...
> > > > Now, this may well be a one-of-a-kind case calling for an ad-hoc
> > > > solution, but if all we need is accept to use ${PREFIX}/share/mk
> > > > for third-party .mk files, this seems a better way to handle
> > > > the problem.
> > >
> > > After >10 years you are apparently the first person to want such a
> > > feature, so this suggests the application is limited :)
> >
> > possibly, yes. Or maybe there were other applications solved with
> > other hacks - e.g. (randomly browsing in /usr/share/mk), do the
> > following really belong there:
> >
> > bsd.info.mk - building GNU Info hypertext system
> > bsd.snmpmod.mk - building modules for the SNMP daemon bsnmpd
> >
> > They don't seem to be a part of the 'base' system unlike all
> > the others.
>
> ? Those are both used by components of the base.
>
> > So... there is not a recursive INSTALL, maybe nobody asked for it,
> > but certainly we have a lot of replicated constructs in the
> > ports' makefiles, and some port maintainers with a lot of patience :)
>
> OK, but I don't see what this has to do with your proposal.
It was a remark on "you are the first one to ask in 10 years so
maybe the application is limited". Sometimes there is a need for
a feature, but people find it easier to use some workaround rather
than asking for it.
The thing with bmake is that probably nothing other than the base
system uses it - most ports use gmake for portability reasons,
so maybe there is limited need to for custom 'mk' directories...
yet if we provide one, hopefully people will start considering
using it rather than workarounds (e.g. hardwiring the common
settings in the individual Makefiles).
cheers
luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070201124052.D84181>