Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove BlueZ dependence #417

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MichalLabedzki
Copy link
Contributor

Libpcap should not use BlueZ userspace headers, because it does not
use BlueZ at all. It use only Linux kernel, but it does not
provide userspace headers. For compatible reason we should use own copy
of headers and try to dynamically detect Linux kernel version and use
proper structures.

This fixes #343.

This is the second try of pull request: #347

Libpcap should not use BlueZ userspace headers, because it does not
use BlueZ at all. It used only Linux kernel, but it does not
provide userspace headers. For compatible reason we should use own copy
of headers and try to dynamically detect Linux kernel version and use
proper structures.
Fix some compilator warnings, avoid one using malloc/free
Also various white characters fixes.
@guyharris
Copy link
Member

Does copying the data structures etc. from the Linux kernel headers make the Bluetooth code GPLv2-licensed? If so, that's a problem, as the rest of libpcap is BSD-licensed (and, unfortunately, licensed with the old 4-clause BSD license).

@mcr
Copy link
Member

mcr commented Feb 15, 2015

guy, I'm trying to see where the copying of headers occured, and I didn't see it. Maybe I missed it.

@guyharris
Copy link
Member

I guess my concern is whether the "our own copy" could get people complaining that we just took GPLed code from Linux or not; if it was a reimplementation from scratch (I don't think "clean room" is necessary), that should suffice.

lkundrak pushed a commit to pignus-project/libpcap that referenced this pull request Nov 27, 2016
kernel-devel package was added because I thought it may resolve bluetooth
related build failure. After addition of dependency packages started building
again however with bluetooth support disabled.

Probably the *right* thing to do would be to move away from bluez
dependency, because code that use bluez-libs anyway. This is currently discussed
upstream.

See: the-tcpdump-group/libpcap#417
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

current libcap does not compile when bluez5 is present
3 participants