From owner-freebsd-ports@FreeBSD.ORG  Thu Mar 16 21:10:15 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: ports@freebsd.org
Delivered-To: freebsd-ports@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 848A316A41F
	for <ports@freebsd.org>; Thu, 16 Mar 2006 21:10:15 +0000 (UTC)
	(envelope-from james@netinertia.co.uk)
Received: from starbug.netinertia.co.uk (starbug.netinertia.co.uk
	[217.147.82.211])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1BB7143D46
	for <ports@freebsd.org>; Thu, 16 Mar 2006 21:10:14 +0000 (GMT)
	(envelope-from james@netinertia.co.uk)
Received: from croydon.netinertia.co.uk ([82.69.247.45] helo=[10.1.0.80])
	by starbug.netinertia.co.uk with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.60 (FreeBSD)) (envelope-from <james@netinertia.co.uk>)
	id 1FJzk1-0005Kr-4M
	for ports@freebsd.org; Thu, 16 Mar 2006 21:10:42 +0000
Message-ID: <4419D414.1070308@netinertia.co.uk>
Date: Thu, 16 Mar 2006 21:09:40 +0000
From: James O'Gorman <james@netinertia.co.uk>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: ports@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-NetI-Spam-Score: -1.4 (-)
Cc: 
Subject: How to deal with large number of patches in a port?
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: Thu, 16 Mar 2006 21:10:15 -0000

Hi,

I'm about to update a port I maintain (sysutils/boxbackup), but due to 
the upstream software not currently being PREFIX-clean, I have a large 
number of patches (29 patches in total) I need to apply to the source 
tree. The majority of them are fairly small (just a few lines), but some 
of them are a bit larger.

I've discussed this with the software developers and the patches have 
already gone into the development tree, but until another release comes 
out I need to patch this release in the port.

I just wanted to check how I should handle this, before I submit the PR. 
Should I add these files to the port directly (i.e. create a directory 
files/patches and put the patches in there, setting PATCHDIR to 
${FILESDIR}/patches), or should I put these on a webserver and set 
PATCHES and PATCH_SITES?

Cheers,

James