From owner-freebsd-ports@FreeBSD.ORG  Wed Dec  3 02:14:55 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 5EFCC1065673
	for <freebsd-ports@freebsd.org>; Wed,  3 Dec 2008 02:14:55 +0000 (UTC)
	(envelope-from pz-freebsd-ports@ziemba.us)
Received: from ziemba.us (208-106-105-148.dsl.static.sonic.net
	[208.106.105.148])
	by mx1.freebsd.org (Postfix) with ESMTP id 343988FC12
	for <freebsd-ports@freebsd.org>; Wed,  3 Dec 2008 02:14:55 +0000 (UTC)
	(envelope-from pz-freebsd-ports@ziemba.us)
Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1])
	by hairball.ziemba.us (8.14.3/8.14.3) with ESMTP id mB32EMlW027117
	for <freebsd-ports@freebsd.org>; Tue, 2 Dec 2008 18:14:22 -0800 (PST)
	(envelope-from pz-freebsd-ports@ziemba.us)
Received: (from mailnull@localhost)
	by hairball.ziemba.us (8.14.3/8.14.3/Submit) id mB32ELTn027116
	for freebsd-ports@freebsd.org; Tue, 2 Dec 2008 18:14:22 -0800 (PST)
	(envelope-from pz-freebsd-ports@ziemba.us)
X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to
	pz-freebsd-ports@ziemba.us using -f
Received: (from news@localhost)
	by hairball.ziemba.us (8.14.3/8.14.3/Submit) id mB32EKru027051
	for treehouse-mail-freebsd-ports@hairball.treehouse.napa.ca.us;
	Tue, 2 Dec 2008 18:14:21 -0800 (PST) (envelope-from news)
From: "G. Paul Ziemba" <pz-freebsd-ports@ziemba.us>
To: freebsd-ports@freebsd.org
Date: Wed, 3 Dec 2008 02:14:20 +0000 (UTC)
Message-id: <gh4q1s$p3b$2@hairball.ziemba.us>
References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au>
Errors-to: "G. Paul Ziemba" <paul+usenet@w6yx.stanford.edu>
Subject: Re: Proposal: mechanism for local patches
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: paul+usenet@w6yx.stanford.edu
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:14:55 -0000

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}/
-- 
G. Paul Ziemba
FreeBSD unix:
 6:11PM  up 2 days,  3:41, 8 users, load averages: 1.58, 1.39, 1.31