A system-independent interface for user-level packet capture
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: https://github.com/the-tcpdump-group/libpcap/pull/417/ |
||
|---|---|---|
| .gitignore | ||
| 0001-man-tcpdump-and-tcpslice-have-manpages-in-man8.patch | ||
| 0002-pcap-config-mitigate-multilib-conflict.patch | ||
| 0003-pcap-linux-apparently-ctc-interfaces-on-s390-has-eth.patch | ||
| 0004-pcap-linux-don-t-use-TPACKETV3-for-memory-mmapped-ca.patch | ||
| 0005-Fix-scaling-of-time-stamps.patch | ||
| libpcap.spec | ||
| sources | ||