From owner-freebsd-ports@FreeBSD.ORG Sat Jan 20 19:13:11 2007 Return-Path: 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 42F7616A408 for ; Sat, 20 Jan 2007 19:13:11 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 94A6813C45B for ; Sat, 20 Jan 2007 19:13:10 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 20 Jan 2007 19:13:08 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO [192.168.1.12]) [129.13.72.169] by mail.gmx.net (mp027) with SMTP; 20 Jan 2007 20:13:08 +0100 X-Authenticated: #5465401 Message-ID: <45B26A02.1040405@gmx.de> Date: Sat, 20 Jan 2007 20:14:10 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.9 (X11/20070120) MIME-Version: 1.0 To: Paul Hoffman References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2007 19:13:11 -0000 Paul Hoffman 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. A more flexible alternative to portsconf is contained in sysutils/bsdadminscripts. > (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. You create patches with diff.