Attachment #143319 for bug #190554

View | Details | Raw Unified | Return to bug 190554
Collapse All | Expand All

Lines 2-21 Link Here

(-)./Makefile (-6 / +14 lines)
2	# $FreeBSD: head/benchmarks/flowgrind/Makefile 356065 2014-06-01 09:00:15Z ohauer $	2	# $FreeBSD: head/benchmarks/flowgrind/Makefile 356065 2014-06-01 09:00:15Z ohauer $
3		3
4	PORTNAME= flowgrind	4	PORTNAME= flowgrind
5	PORTVERSION= 0.6.1	5	PORTVERSION= 0.7.1
6	PORTREVISION= 1
7	CATEGORIES= benchmarks	6	CATEGORIES= benchmarks
8	MASTER_SITES= https://launchpad.net/flowgrind/trunk/${PORTNAME}-0.6.1/+download/
9		7
10	MAINTAINER= lars@eggert.org	8	MAINTAINER= lars@eggert.org
11	COMMENT= Measure throughput and other metrics for TCP	9	COMMENT= Measure throughput and other metrics for TCP
12		10
		11	LICENSE= GPLv3
		12
13	LIB_DEPENDS= libxmlrpc++.so:${PORTSDIR}/net/xmlrpc-c \	13	LIB_DEPENDS= libxmlrpc++.so:${PORTSDIR}/net/xmlrpc-c \
14	libgsl.so:${PORTSDIR}/math/gsl \	14	libgsl.so:${PORTSDIR}/math/gsl \
15	libpcap.so.1:${PORTSDIR}/net/libpcap	15	libpcap.so:${PORTSDIR}/net/libpcap
		16
		17	USE_GITHUB= yes
		18	GH_ACCOUNT= ${PORTNAME}
		19	GH_TAGNAME= ${PORTNAME}-${PORTVERSION}
		20	GH_COMMIT= 14b0578
16		21
17	USES= tar:bzip2	22	USE_AUTOTOOLS= autoconf
18	GNU_CONFIGURE= yes	23	GNU_CONFIGURE= yes
19	CONFIGURE_ARGS= --enable-debug	24	CONFIGURE_ARGS= --enable-pcap --enable-gsl
		25
		26	post-patch:
		27	cd ${WRKSRC} && ${AUTORECONF} -i
20		28
21	.include <bsd.port.mk>	29	.include <bsd.port.mk>

Lines 1-2 Link Here

(-)./distinfo (-2 / +2 lines)
1	SHA256 (flowgrind-0.6.1.tar.bz2) = a0d0f34dc27b4ede320aac913bb2179fc1a307cfb9d3218b9d64d0aeac8a2cef	1	SHA256 (flowgrind-0.7.1.tar.gz) = c82db7f91e4d3c69012bfac26c8627137dadeb0f344f8be4fa214c3bc6213f7f
2	SIZE (flowgrind-0.6.1.tar.bz2) = 211922	2	SIZE (flowgrind-0.7.1.tar.gz) = 133890

Lines 1-11 Link Here

(-)./pkg-descr (-10 / +6 lines)
1	Flowgrind grinds flows among hosts in your network. It is a tool similar	1	Flowgrind is an advanced TCP traffic generator for testing and
2	to iperf, netperf to measure throughput and other metrics for TCP.	2	benchmarking Linux, FreeBSD, and Mac OS X TCP/IP stacks. In
3	Flowgrind is split into two components: the flowgrind daemon and the	3	contrast to similar tools like iperf or netperf it features a
4	flowgrind controller. Using the controller, flows between any two systems	4	distributed architecture, where throughput and other metrics are
5	running the flowgrind daemon can be setup (third party tests). At regular	5	measured between arbitrary flowgrind server processes.
6	intervals during the test the controller collects and displays the
7	measured results from the daemons. It can run multiple flows at once with
8	the same or different settings and individually schedule every one.
9	Test and control connection can optionally be diverted to different interfaces.
10		6
11	WWW: http://launchpad.net/flowgrind	7	WWW: http://flowgrind.net/

Return to bug 190554