Import sysutils/multitime, written by and ported by Laurence Tratt.

OK sthen@

sysutils/multitime/Makefile

@@ -0,0 +1,26 @@
+# $OpenBSD: Makefile,v 1.1.1.1 2012/09/27 15:04:22 edd Exp $
+
+COMMENT =		time multiple executions of a command
+
+DISTNAME =		multitime-1.0
+CATEGORIES =		sysutils
+
+HOMEPAGE =		http://tratt.net/laurie/src/multitime/
+
+MAINTAINER =		Laurence Tratt <laurie@tratt.net>
+
+# BSD / MIT
+PERMIT_PACKAGE_CDROM =	Yes
+PERMIT_PACKAGE_FTP =	Yes
+PERMIT_DISTFILES_CDROM =Yes
+PERMIT_DISTFILES_FTP =	Yes
+
+MASTER_SITES =		${HOMEPAGE}releases/
+
+CONFIGURE_STYLE =	gnu
+
+NO_REGRESS =		Yes
+
+WANTLIB =		c m
+
+.include <bsd.port.mk>

sysutils/multitime/distinfo

@@ -0,0 +1,2 @@
+SHA256 (multitime-1.0.tar.gz) = /a9N+mYngzJXHKYSK2D2gmIea+8+yTM0YY19eoqfXMg=
+SIZE (multitime-1.0.tar.gz) = 49284

sysutils/multitime/pkg/DESCR

@@ -0,0 +1,12 @@
+Unix's 'time' utility is a simple and often effective way of measuring how
+long a command takes to run ('wall time'). Unfortunately, running a command
+once can give misleading timings: the process may create a cache on its first
+execution, running faster subsequently; other processes may cause the command
+to be starved of CPU or IO time; etc. It is common to see people run 'time'
+several times and take whichever values they feel most comfortable with.
+Inevitably, this causes problems.
+
+multitime is, in essence, a simple extension to time which runs a command
+multiple times and prints the timing means, standard deviations, mins,
+medians, and maxes having done so. This can give a much better understanding
+of the command's performance.

sysutils/multitime/pkg/PLIST

@@ -0,0 +1,3 @@
+@comment $OpenBSD: PLIST,v 1.1.1.1 2012/09/27 15:04:22 edd Exp $
+@bin bin/multitime
+@man man/man1/multitime.1