From owner-freebsd-ports@FreeBSD.ORG  Wed Dec  3 02:25:04 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DCC941065673
	for <freebsd-ports@freebsd.org>; Wed,  3 Dec 2008 02:25:04 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158])
	by mx1.freebsd.org (Postfix) with ESMTP id AE8F48FC17
	for <freebsd-ports@freebsd.org>; Wed,  3 Dec 2008 02:25:04 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: by syn.atarininja.org (Postfix, from userid 1001)
	id EEEC45C17; Tue,  2 Dec 2008 21:25:03 -0500 (EST)
Date: Tue, 2 Dec 2008 21:25:03 -0500
From: Wesley Shields <wxs@FreeBSD.org>
To: paul+usenet@w6yx.stanford.edu
Message-ID: <20081203022503.GC8753@atarininja.org>
References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au>
	<gh4q1s$p3b$2@hairball.ziemba.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <gh4q1s$p3b$2@hairball.ziemba.us>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-ports@freebsd.org
Subject: Re: Proposal: mechanism for local patches
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2008 02:25:04 -0000

On Wed, Dec 03, 2008 at 02:14:20AM +0000, G. Paul Ziemba wrote:
> john.marshall@riverwillow.com.au (John Marshall) writes:
> 
> >On Tue, 02 Dec 2008, 21:07 +0300, Dmitry Marakasov wrote:
> >> I think the most convenient way of implementing this is having
> >> a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*)
> >> or single level ${PORTNAME}/patch-*) and a single variable that makes
> >> port system look there for patches in addition to ${PATCHDIR}.
> 
> >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}/

It uses UNIQUENAME, which is documented in Mk/bsd.port.mk.

-- WXS