Date: Wed, 3 Dec 2008 02:24:45 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Proposal: mechanism for local patches Message-ID: <20081203022445.13cd2100@gumby.homeunix.com> In-Reply-To: <gh4q1s$p3b$2@hairball.ziemba.us> References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au> <gh4q1s$p3b$2@hairball.ziemba.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Dec 2008 02:14:20 +0000 (UTC)
"G. Paul Ziemba" <pz-freebsd-ports@ziemba.us> wrote:
> john.marshall@riverwillow.com.au (John Marshall) writes:
>
> >Or keep local patches under /var/db/ports/<port> rather than
> >building a new tree?
>
> Hmm. I haven't really understood the way directories get named in
> /var/db/ports/ - what happens when there is a collision in the
> base name of two ports? It seems less obvious than
> /<foo>/${CATEGORY}/${PORTNAME}/
The names are not labelled by port names, but rather by UNIQUENAME
# UNIQUENAME - A name for your port that is globally unique. By default,
# this is set to ${LATEST_LINK} when LATEST_LINK is set,
# and to ${PKGNAMEPREFIX}${PORTNAME} otherwise.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081203022445.13cd2100>