Am 19.12.19 um 18:26 schrieb Stefan Brüns:
Just to shed some light on why Python requires bluez-devel:
Pythons 'socket' module has optional support for the AF_BLUETOOTH protocol family, but it is only enabled when bluez-devel is available during build.
OK, this explains things ;-) However, I guess using socket() with AF_BLUETOOTH is exactly the low-level access that bluez upstream frowns upon and that is basically discouraged by dropping the deprecated binaries and letting bluetoothd handle all this stuff.
As socket is a dependency of many other modules it is built as part of python3-base. python3-base is a build dependency of many other packages, probably 2/3rd of all TW packages depend on it (directly or indirectly). Most importantly, python3-base is also a build dependency of bluez.
The bluez-devel BuildRequires was moved from python3 to python3-base to make AF_BLUETOOTH available in pythons socket, but as it introduces a build loop it was removed again.
Maybe just copying /usr/include/bluetooth/bluetooth.h from bluez-devel to the python package and using it during build is probably a way to work around the build loop issue. I doubt that anyone is linking against libbluetooth nowadays, it's basically just a collection of some endianness byteswap functions. Are there actual users of AF_BLUETOOTH from python? (just being curious...) Thanks for the explanation, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org