you don't have many packages, and it was hard for me to find something for nitpicking, but I still managed.
# openiked depends=('glibc' 'libevent' 'openssl') it's hard to imagine a system without glibc installed, but I've seen the same packages in our repositories. so it's ok.
It can be a little confusing for new users because the tooling will print warnings about this:
openiked W: Dependency glibc included but already satisfied openiked W: Dependency openssl included but already satisfied
But Arch's packaging policy says "Do not rely on transitive dependencies in any of the PKGBUILD#Dependencies, as they might break if one of the dependencies is updated."
These two things seem to be in conflict with each other, so I went with the policy statement as the deciding rule.
makedepends=('linux-headers' 'bison' 'cmake') 'bison' is in base-devel group so no need to include it here.
I can remove that, but it also sounds like a transitive dependency. Is base-devel an exception? Maybe the documentation on this issue could be clarified a bit.
In the last two years I've submitted just over 150 patches to the Arch bug tracker: https://bugs.archlinux.org/index.php?opened=32638&status%5B%5D=
oh this is very cool.
(They've probably gotten sick of seeing my name in those bug report emails by now, huh?)
Anyway, I appreciate your input.