From owner-freebsd-ports@FreeBSD.ORG Sat Feb 28 20:20:18 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 412DA25C for ; Sat, 28 Feb 2015 20:20:18 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 177C227A for ; Sat, 28 Feb 2015 20:20:17 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t1SKL9wu024392 for ; Sat, 28 Feb 2015 12:21:09 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <54F16F90.2070600@FreeBSD.org> References: <54F09CC7.1000407@astart.com>, <54F16F90.2070600@FreeBSD.org> From: "Chris H" Subject: Re: Generating port changes easily Date: Sat, 28 Feb 2015 12:21:09 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2015 20:20:18 -0000 On Sat, 28 Feb 2015 18:34:40 +1100 Kubilay Kocak wrote > On 28/02/2015 3:35 AM, Patrick Powell wrote: > > I have made some modifications to a port - couple of lines in the > > Makefile, and an updated pkg-plist. > > > > Once upon a time I was shown a script (run_this_script?) to help with > > updating a port. > > > > 1. Copy the original files in the port to XXX.orig (or something) > > For example cp Makefile Makefile.orig > > 2. Make your changes > > For example: vi Makefile .... > > 3. Now run this script which will generate a DIFF file which can be > > posted: > > run_this_script ... >/tmp/changes.shar ? > > run_this_script ... >/tmp/diffs ? > > 4. Post the generated file to bugzilla with an update request. > > > > Ummm... is there such a 'run_this_script' or am I indulging in wishful > > thinking? > > > > If the changes you make are in the ports files, porttools has a 'port > diff' command (which uses a reference ports tree to create diffs > against. You can use /usr/ports as that reference, and in fact I believe > that is the default. > > You can then just port diff > path-to-patch-file.diff, ready for > attachment into a new bugzilla issue. > > If the patch is against WRKSRC source code, you can > > a) cp WRKSRC/file WRKSRC/file.orig > b) edit file > c) make makepatch (from the port dir) > > makepatch recursively searches WRKSRC for *.orig files, and > automatically creates correctly named patch-foo patch files in /files > for you. > > Hope that helps koobs' reply got me to thinking. So I did a little searching around in ports/Tools/scripts and found, I think, exactly what you were referring/hoping for; update-patches Give it a look. It's intended to work almost exactly as you described. HTH --Chris > > -- > > koobs > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"