2.61_1net-mgmtΣ=3 2.61_1Version of this port present on the latest quarterly branch.
BROKEN: unknown type name 'u_int64' DEPRECATED: marked BROKEN for more than 6 months This port expired on: 2020-01-14 IGNORE: is marked as broken: unknown type name 'u_int64'
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
This package is a port of TAMU's extract program from NetLogger to look
at flow data instead of netlogger data. Blame Larry for it's faults, not
TAMU. Blame me for the FreeBSD port, not Larry :-)
If you don't already have a good guess what this program does and what
data it is looking for, the odds are that it isn't going to be of much
help to you. This program only works on Cisco flow data as captured
with Mark Fullmer's flowtools package. If you don't have that, get that
first, then look at this program.
In order for this to compile you will need flowtools from Mark
Fullmer's (net-mgmt/flow-tools port).
WWW: http://answers.uchicago.edu/page.php?id=19876
Remove expired ports:
2020-01-14 net-mgmt/flow-extract: marked BROKEN for more than 6 months
2020-01-14 textproc/pootle: Unamaintained, marked BROKEN for more than 5 months
Support LIBS like LDFLAGS.
- Add LIBS="${LIBS}" to MAKE_ENV and CONFIGURE_ENV.
- Add an option helper for LIBS.
- Adjust all ports that already use LIBS. Also remove references to
PTHREAD_CFLAGS and PTHREAD_LIBS while here.
- Some ports did not support having a LIBS environment variable and
required additional patches.
Somewhat simplified a linker command line looks like:
${CC} ${src_LDFLAGS} ${LDFLAGS} ${src_LIBS} ${LIBS}
where src_LDFLAGS and src_LIBS are controlled by upstream and LDFLAGS and
LIBS can be controlled by us. If possible -L and -l flags need to be
(Only the first 15 lines of the commit message are shown above )
For ports maintained by ports@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
Say hello to the new "net-mgmt" category. There are probably more
ports that belong here than the ones I have identified and moved in
this, first, pass.
Approved in principle by: marcus