https://bugzilla.redhat.com/show_bug.cgi?id=1650987 --- Comment #10 from Fabio Valentini <decathorpe@xxxxxxxxx> --- To create a patch, I usually do it with a temporary git repository (it makes generating the patches easier than plain "diff"): 1) Extract the upstream tarball 2) Initialise a git repository with pristine contents: $ git init && git add . && git commit -m import 3) Make my modifications 4) Generate the patch (I tend to number mine from 00 upwards): $ git diff --patch > $HOME/rpmbuild/SOURCES/00-location.patch 5) Include the patch in the .spec file: Patch0: 00-location.patch 6) Tell autosetup which patch level to apply: %autosetup -n %{srcname}-%{version} -p1 7) Proceed as usual (patches are included in the .src.rpm file when running rpmbuild -bs *.spec). I've added a patch for the Makefile and a .spec file with the necessary modifications for you to inspect in the attached .src.rpm file. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
