so i'm reviewing the recent alpha releases of nmap and i've run into a small snag; configure is now checking for libpcap => 0.9.4. if the version is lower, then it begins to build its own rolled version of libpcap. nmap seems to want this now.
i'd much rather prefer that nmap uses base's libpcap(3), and its been nice removing the local patches for nmap in the port. i could obviously maintain a patch to configure and whatever else, but another question arises: how come base's libpcap(3) hasn't been bumped? i've gone through -current's libpcap(3) and most everything was pulled in from tcpdump.org's pcap library/api, for 4.0 at least. maybe this is not the right place to ask, but what about a bump in src/lib/libpcap/VERSION? or does anybody not care if we use nmap's rolled libpcap+patches (from tcpdump.org). or should i just patch away again. advice? cheers, okan
