New comment by freddylist on void-packages repository

https://github.com/void-linux/void-packages/pull/39360#issuecomment-1251000214

Comment:
> I think it's better to patch their Makefile to have let's say -include config.mk and put the option there. Whoever want some custom option could put the config into files directory. With that approach, we won't need to care for nnn's change in build option whatsoever. As for build dependencies, just add them all. nnn is always a leaf (as in graph) packages.

Sorry if this is a dumb question, but where would that be documented? Shouldn't users just place patch files in the `nnn` template's `patches/` directory?

As for build options, if I was trying to manage `nnn` with `xbps-src`, I would at least except the options to enable icon support to be present in `xbps-src show-options nnn`, as it is a popular thing to compile `nnn` with.