From owner-freebsd-questions@FreeBSD.ORG Tue Mar 23 15:16:50 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF25C106566C; Tue, 23 Mar 2010 15:16:50 +0000 (UTC) (envelope-from prvs=691a0532e=pschmehl_lists@tx.rr.com) Received: from ip-002.utdallas.edu (ip-002.utdallas.edu [129.110.20.108]) by mx1.freebsd.org (Postfix) with ESMTP id 9D2CB8FC1F; Tue, 23 Mar 2010 15:16:50 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Al4FAENxqEuBbgogTmdsb2JhbACbNwEBIkS7foR9BIMe X-IronPort-AV: E=Sophos;i="4.51,295,1267423200"; d="scan'208";a="27444407" Received: from zxtm01.utdallas.edu (HELO utd65257.utdallas.edu) ([129.110.10.32]) by ip-002.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Mar 2010 09:47:49 -0500 Date: Tue, 23 Mar 2010 09:47:49 -0500 From: Paul Schmehl To: glarkin@FreeBSD.org, freebsd-questions@freebsd.org Message-ID: <83BEEB5783CC06E1C802658D@utd65257.utdallas.edu> In-Reply-To: <4BA40295.4090006@FreeBSD.org> References: <20100319170159.GB71392@slackbox.erewhon.net> <20100319200130.GE265@comcast.net> <3D386E86A152519AA850205C@utd65257.utdallas.edu> <8B123BA51B43B4AAC86E0F3C@utd65257.utdallas.edu> <20100319220126.GH265@comcast.net> <2C40431FF3AE42C7B0234A97@utd65257.utdallas.edu> <20100319222143.GI265@comcast.net> <4BA40295.4090006@FreeBSD.org> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Paul Schmehl , "corky1951@comcast.net >> Charlie Kester" Subject: Re: Elegant way to hack port source X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2010 15:16:51 -0000 --On Friday, March 19, 2010 19:02:45 -0400 Greg Larkin wrote: > > Here's something else that I've found really useful as a port creator, > maintainer and troubleshooter. If I want to make some additional > changes to a source file that is patched by a file stored in > files/patch-...., I'll do this: > > make patch # extracts source and patches files > cd work/foobar/... ># Now make additional edits in patched file, leaving the ># .orig file alone > cd ../back/to/port/directory > make makepatch > > The makepatch target recurses through the work/foobar directory and > creates diffs for all file.ext/file.ext.orig pairs. It writes them to > the files/ directory with the patch- prefix on each so the patch target > processes them. > > The only thing to watch out for here, is that makepatch has its own file > naming convention that doesn't always mirror the port creator's. For > instance, some ports have patch files named "patch-aa", "patch-ab", etc. > The makepatch target will recreate them with filenames based on the > directory and filename of the file to be patched during the build. > > Hope that helps, Man, does it ever. Thanks for that. Which brings me to an obvious question. Where can I go to find out what all of the make targets are? Is it in /usr/ports/Mk/? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson