Created attachment 185727 [details] shar file for dns/unbound-python dns/unbound is built without python support by default. This slave port adds python support, to allow python modules for Unbound to be ported and packaged.
I don't think it is the right solution to have a slave port for just the python option difference. The problem: in case some users will want it with PYTHON=on and some - with PYTHON=off, this will cause conflicts. The right solution: to split out the python binding from dns/unbound into a separate port, dns/py-unbound. This way dependent ports can use any involved packages without conflicts. Please correct this, and create a dns/py-unbound instead. Regards, Yuri
dns/unbound has configure options: /usr/ports/dns/unbound/work/unbound-1.7.0/configure --help: --with-pyunbound build PyUnbound, or --without-pyunbound to skip it. (default=no) --with-pythonmodule build Python module, or --without-pythonmodule to disable script engine. (default=no)
Any news here?