FS#66763 - [unbound] provide python module
Attached to Project:
Community Packages
Opened by Vladimir (_v_l) - Sunday, 24 May 2020, 07:32 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Saturday, 24 July 2021, 16:55 GMT
Opened by Vladimir (_v_l) - Sunday, 24 May 2020, 07:32 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Saturday, 24 July 2021, 16:55 GMT
|
Details
Description: unbound upstream provides python module (option
'--with-pyunbound' has to be passed to 'configure' script)
with 'unbound' sources but currently it is not build and not
provided. There is 'python-unbound' package in AUR and it is
used by 'hash-slinger' also available in AUR. The 'unbound'
package could provides two packages: 'unbound' and
'python-unbound'.
|
This task depends upon
Closed by Bruno Pagani (ArchangeGabriel)
Saturday, 24 July 2021, 16:55 GMT
Reason for closing: Implemented
Additional comments about closing: unbound 1.13.1-2 thanks to https://github.com/NLnetLabs/unbound/pul l/511
Saturday, 24 July 2021, 16:55 GMT
Reason for closing: Implemented
Additional comments about closing: unbound 1.13.1-2 thanks to https://github.com/NLnetLabs/unbound/pul l/511
However I find that enabling `--with-pyunbound` or `--with-python-module` makes libunbound.so link against libpython3.8.so.1.0. That's really too big a hard dependency for such as small package as unbound so that'll have to live in a separate package. Since I have no interest in maintaining this, it's probably best to leave this on the AUR.
But please provide a patch against our PKGBUILD if you know how to enable python bindings without making libunbound.so link against libpython.so.
Cheers.
I made some "workaround" (very "dirty" trick, like 'vim' package do) to provide python module but before present it I would like to understand why there are two python related options. I opened issue on github (https://github.com/NLnetLabs/unbound/issues/242) and hope to get answer, may be the linkage against 'libpython' is a bug.