Using customizepkg with pakku

Install customizepkg-git (other variants are available.) Versions used for this test: which 2.21-5.1 and customizepkg-git 59.852c335-1

Create these two files:

1. /etc/customizepkg.d/which:

patch#which.c#testpatch.patch
replace#build#patch -Npwhich.c -i testpatch.patch#  patch -N which.c -i ../testpatch.patch

2. /etc/customizepkg.d/which.files/testpatch.patch:

--- which.c
+++ which.c
@@ -47,7 +47,7 @@
   fprintf(out, "If the options --read-alias and/or --read-functions are specified then the\n");
   fprintf(out, "output can be a full alias or function definition, optionally followed by\n");
   fprintf(out, "the full path of each command used inside of those.\n\n");
-  fprintf(out, "Report bugs to <which-bugs@gnu.org>.\n");
+  fprintf(out, "Report bugs to <which-bugs@gnu.org>. customizepkg - testing \n");
 }

Edit /etc/pakku.conf: PreBuildCommand = customizepkg --modify

$ pakku -Sn which
$ which --help

...and the last line should now read...

Report bugs to <which-bugs@gnu.org>. customizepkg - testing

Nb: "which" is a small easily built package with a relatively simple build process - not all packages are this easy to modify! It was easier to use pakku -Sz then run customizepkg --modify, makepkg -o and makepkg -e manually to break down the process when creating the config. If you use diff -u you can edit the --- and +++ lines at the top to alter the filenames and paths although it may not be required. The patch line produced by this version of customizepkg has to be replaced as it doesn't work. There are some unmerged PR's on the repo that might help. If you're already familiar with customizepkg you probably know more than me!