Date: Tue, 24 Feb 2004 11:11:02 +0100 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Mark Linimon <linimon@lonesome.com> Cc: ports@FreeBSD.org Subject: Re: how to determine whether a port is a slave port? Message-ID: <403B2336.1030607@fillmore-labs.com> In-Reply-To: <Pine.LNX.4.44.0402240012310.27707-100000@pancho> References: <Pine.LNX.4.44.0402240012310.27707-100000@pancho>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Linimon wrote:
> One of the things that I would like to have available for the
> database in my ports monitoring code is an indication of whether
> or not a port is a slave port. The Porter's Handbook recommends
> that the MASTERDIR makevar be used to establish that, but does
> not make it clear whether its use is mandatory or not. However,
> there are over 300 ports that do not seem to use this convention.
> Most seem to use the "${.CURDIR}/.." convention, although a few
> seem to use PORTSDIR directly.
>
> So, without wanting to start a bikeshed, are these just remnants
> of a time before MASTERDIR was introduced? Is there a consensus
> on how slave ports ought to be handled?
Since FreshPorts is having problems with that too, I suggest that
a port is a slave port if and only if MASTERDIR is set, and to let
us fix the other ports. That would make it easier for portlint too.
Concerning ${.CURDIR}/../.. vs. ${PORTSDIR} I'm undecided. Whats the
problem with having both?
-Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?403B2336.1030607>