https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793
--- Comment #6 from Kubilay Kocak <ko...@freebsd.org> --- (In reply to SBB from comment #5) That's a great effort (and correct, for a patch against the upstream sources), though what is preferable is a patch against the port itself, creating a files/patch-* file. Here's how you do it: 1) # cd /path/to/category/port 2) # make clean extract 3) # cd work/path/to/file 4) # cp file file.orig 5) edit file 6) go back to port directory 7) # make makepatch You'll find a brand new file created for you in files/ :) Then just `svn diff` > patch.diff in the port directory to produce a diff against the port There is documentation on this, but it's a little ambiguous: https://www.freebsd.org/doc/en/books/porters-handbook/slow-patch.html Also, bonus points if you patch in the entire upstream commit (including comment) You can grab that here: https://github.com/grisha/mod_python/commit/5bb5d6d0113f6bbd72966a5c1f3e6d40c2e9c8fd.patch -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
