Generating port changes easily
papowell at astart.com
Tue Mar 3 15:22:01 UTC 2015
On 02/27/15 23:34, 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
>> 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
> 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
Excellent suggestions, both. I tried port diff AND make makepatch - both
seemed to work as advertised.
Thanks for the help!
Patrick Powell Astart Technologies
papowell at astart.com 1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
More information about the freebsd-ports