From owner-freebsd-ports@FreeBSD.ORG  Sat Jan 20 05:38:01 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freeBSD-ports@freebsd.org
Delivered-To: freeBSD-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C799716A400
	for <freeBSD-ports@freebsd.org>; Sat, 20 Jan 2007 05:38:01 +0000 (UTC)
	(envelope-from swhetzel@gmail.com)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186])
	by mx1.freebsd.org (Postfix) with ESMTP id 618A813C44C
	for <freeBSD-ports@freebsd.org>; Sat, 20 Jan 2007 05:38:01 +0000 (UTC)
	(envelope-from swhetzel@gmail.com)
Received: by nf-out-0910.google.com with SMTP id k27so670043nfc
	for <freeBSD-ports@freebsd.org>; Fri, 19 Jan 2007 21:38:00 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=bRzRfhv4IWYlh0zT4fG6zLnZmbJjOlUk838OZ/4leQYCyZ2T2eMtDQqfTDieKsXh1uabH168KP+udu7AS3bSs8S/SwxHixDOT6Syop5WNJhK4iTXiG2rxySIVGt/HoTJjRsChDC7OGXKcxDCxhsOw3nze2oyC82XSy3IjAKTUUs=
Received: by 10.82.172.15 with SMTP id u15mr1862978bue.1169271479553;
	Fri, 19 Jan 2007 21:37:59 -0800 (PST)
Received: by 10.82.186.2 with HTTP; Fri, 19 Jan 2007 21:37:59 -0800 (PST)
Message-ID: <790a9fff0701192137y703108i421c05422eda39a7@mail.gmail.com>
Date: Fri, 19 Jan 2007 23:37:59 -0600
From: "Scot Hetzel" <swhetzel@gmail.com>
To: "Paul Hoffman" <phoffman@proper.com>
In-Reply-To: <p06240841c1d75354626b@10.20.30.108>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <p06240841c1d75354626b@10.20.30.108>
Cc: freeBSD-ports@freebsd.org
Subject: Re: Modifying a port and keeping the mods across updates
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: Sat, 20 Jan 2007 05:38:01 -0000

On 1/19/07, Paul Hoffman <phoffman@proper.com> wrote:
> Greetings again. I have a two-part question that may be a ports FAQ,
> but I couldn't find such a beast.
>
> (1) For a particular port, I need to change the the MAKE_ENV to make
> it build the way I want. What is the proper way to do this that will
> live beyond the next time I do a cvsup? That is, editing the Makefile
> works just fine, but I want something that will live if the Makefile
> gets reverted.
>
Use the sysutils/portconf port and define the apporiate variable in
PREFIX/etc/ports.conf.

> (2) For a particular port, I need to patch a particular source file.
> This is a patch that will probably be in a future release. Same
> question as above: what's the proper way to do this that will live
> beyond the next cvsup? I know how to use 'patch' to apply patches,
> but not yet to create them.
>
To create a patch you first need to create a backup of the original
file, then create the diff.

cp file.c file.c-orig
<make changes to file.c
diff -u file.c-orig file.c > patch-file.c

Then place the patch file into /usr/ports/<category>/<portname>/files.

Scot
-- 
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.