Arch Linux User Repository

config.h is optional by design. The way the PKGBUILD is written is so that you can extend the source array with your own config.h but don't have to. You can also can add patches there.
As has been noted, the PKGBUILD only copies things it finds in the source array, while already assuming that it would be in the PKGBUILD's directory.
If anyone of you still has issues feel free to drop me an email.

I have one st build with easy changeable colorscheme, check that out also. https://aur.archlinux.org/packages/st-patched-git/

https://d.filebox.moe/ujgwgdc

Can someone please take a look and tell me what I'm doing wrong ?

I have a few questions/comments about this package

#1: You remove the terminfo file; but st-git needs its terminfo. The one packaged with current ncurses does not work with st-git. We need to install that terminfo somewhere.

#2 Your various FLAGS alterations should probably be submitted upstream, not here, no? However, it looks like they were all implemented by now, with the exception of CPPFLAGS, and I assume they did that for a reason. You can take those out of the PKGBUILD.

#3 While we're taking things out of the PKGBUILD, your personal customizations to config.h should probably go in a config.h, not the global AUR package.

#4 Thank you for switching to the tag versions rather than date, but you forgot to update SRCINFO!

great idea prash, I included that.

Please replace line 49 with
patch -Np1 <"$srcdir/$(basename ${file})"

That way, users can include URLs for patches hosted at suckless.org. They might have to modify the sha1sums array, but that's something they can figure out while modifying the source array.

I was running into an issue where I built the package which created a config.h and later on I patched the config.def.h but it was not used due to the now existing config.h

I just deleted the config.h and the package recreated it taking the now patched version of config.def.h

Just something to be aware of if you are applying patches and redoing the makepkg.

So where should we put config.h and diff patches? The directory with PKGBUILD doesn't seem to work.

config.h is optional by design. The way the PKGBUILD is written is so that you can extend the source array with your own config.h but don't have to. You can also can add patches there.
As has been noted, the PKGBUILD only copies things it finds in the source array, while already assuming that it would be in the PKGBUILD's directory.
If anyone of you still has issues feel free to drop me an email.

fedemp:

that's beacause `"${source[@]}"` in PKGBUILD points to git://git.suckless.org/st instead to your clone directory.

If you use $AURDEST you might be able to modify PGKBUILD to use files from there....I haven't figured out how yet...

Just a tip. If you want a brighter red cursor change " 1 " to " 9 " in " -e '/int defaultcs/s/= .*/= 1;/' \ " for other colours http://git.suckless.org/st/tree/config.def.h