libknot and libzscanner and libdnssec all link to libcap-ng unnecessarily
i think libcap-ng is only needed by knot itself, not its constitutent libraries.
however, the knot build process links the libraries to libcap-ng unnecessarily, because AC_SEARCH_LIBS([capng_apply], [cap-ng])
(in configure.ac
) ends up adding it directly to LIBS
.
by contrast, knot links to liburcu
without the built libraries linking to it.
Perhaps libcap-ng
should be treated more like liburcu
and less like the other libraries that all the knot libs actually do link to.