how to efficiently work through generating patches using git and macports build process?

[Marius Schamschula]

On Aug 30, 2017, at 8:33 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
> On Aug 30, 2017, at 10:44, Ken Cunningham wrote:
> 
>> When trying to fix broken ports, I have so far been using the method of copying the source file to source.orig, editing the source files in place, and then noting the files I worked on, to individually diff them at the end to individual patch files.
>> 
>> It's easy to understand, but not super efficient, especially when I make a number of changes in different files.
> 
> This basically describes what I do. I'm happy with this process because I understand it.
> 

I do a variation on this scheme as well. I have two scripts

1) to create the .orig file (using path information from port and the relative path)

2) to generate the diff and place the properly named patch file in the appropriate files directory.

Marius
--
Marius Schamschula




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20170831/0da28e7e/attachment.html>