https://bugzilla.redhat.com/show_bug.cgi?id=1762673
Robert-André Mauchin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from Robert-André Mauchin <[email protected]> --- IanHarvey commented on Nov 2 bluepy uses a copy of some source files from the BlueZ project to build a C language executable, bluepy-helper, which is a shim between Python and the kernel's Bluetooth interface. It does not build or install any binaries which are the same as what the BlueZ package provides - so at no point would you have a "bluepy" and a "system" version of the same thing on your disk. Note that there isn't a realistic way to "use the system's BlueZ" - BlueZ itself provides various command line executables and daemons, but there isn't a library or low-level interface suitable for calling from Python. (I looked at the D-Bus interface but at the time it was very incomplete, and its availability is likely to vary a lot between distributions). Take a look at https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/python-bluepy too, you probably will need to do the same edits on the makefile to use Fedora default build flags by setting %set_build_flags before building. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
