and breaks with newer setuptools.
the repo that this port currently uses has seen no activity for a
while; patch is taken from the fork "pcapy-ng". this should move across
to pcapy-ng anyway because this old one will fail with Python 3.10; not
doing that now as various deps will need adjusting for paths
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
Pcapy is a Python extension module that enables software written in Python
to access the routines from the pcap packet capture library.
Pcapy is most useful when used together with a packet handling package such
as Impacket, a collection of Python classes for contructing and dissecting
network packets.