tcpdump-3.9.4-r2 depends on net-libs/libpcap but it should be virtual/libpcap so that anyone who uses an alternative libpcap (like the libpcap-ringbuffer ebuild) doesn't have an issue
No, it really shouldn't until Bug 117898 is fixed. Meanwhile, the libpcap-ringbuffer thing is broken and package.masked.
(In reply to comment #1) > No, it really shouldn't until Bug 117898 is fixed. Meanwhile, the > libpcap-ringbuffer thing is broken and package.masked. > libpcap-ringbuffer is not broken. People (myself included) are using it everyday. If you look at comment #20 on Bug 117898, you see that the TEXTRELs are not coming from libpcap-ringbuffer, but from broken header files in /usr/include. At least, that's how I understand it. Perhaps I am wrong, in which case you could enlighten me as to why libpcap-ringbuffer remains masked. Regardless of the libpcap-ringbuffer status, net-libs/libpcap specifically provides virtual/libpcap, so why does it do that if the rest of the ebuilds (snort, tcpdump, etc.) aren't going to make use of the virtal? That seems silly to me. As much as I want to reopen this bug, I'll leave it for the time being so I can perhaps better understand why so simple a change cannot be made.
