usr.sbin/blacklist{d,ctl}: Use libblacklist

[ivy]

Summary

This fixes the build when WITHOUT_BLOCKLIST=yes is set.

MFC after: 2 weeks
Sponsored by: https://www.patreon.com/bsdivy

[jlduran]

Give me some time to test it, but I think it is better if we just update share/mk/src.opts.mk (and regenerate the manual page afterwards):

.if ${MK_BLOCKLIST} == "no"
MK_BLACKLIST:=	no
.endif

.if ${MK_BLOCKLIST_SUPPORT} == "no"
MK_BLACKLIST_SUPPORT:=	no
.endif

The problem is that libblacklist should not be used by anything in base, not even blacklistd/blacklistctl. It is only there for some of the ports that still use it (which reminds me I should start submitting the patches). there are some incompatibilities between the two besides just the name.

Thank you for the heads up!

[ivy]

that sounds reasonable. note this blocks D56087, so i'm interested in the result.

[jlduran]

In D56117#1283524, @ivy wrote:

that sounds reasonable. note this blocks D56087, so i'm interested in the result.

Also note that anything *blacklist*-related should be gone in 16.0. I'll work on updating the ports ASAP.

[jlduran]

Please see: D56118.

[ivy]

closing in favour of the other diff