multitime: init at 1.4

This commit is contained in:
Kirill Elagin 2019-11-21 12:50:03 +03:00
parent 6cffb5072f
commit 0d774cdfd4
No known key found for this signature in database
GPG key ID: 914505DF3B3B7B76
2 changed files with 41 additions and 0 deletions

View file

@ -0,0 +1,39 @@
{ stdenv, fetchFromGitHub, autoreconfHook }:
stdenv.mkDerivation rec {
pname = "multitime";
version = "1.4";
src = fetchFromGitHub {
owner = "ltratt";
repo = pname;
rev = "${pname}-${version}";
sha256 = "1p6m4gyy6dw7nxnpsk32qiijagmiq9vwch0fbc25qvmybwqp8qc0";
};
nativeBuildInputs = [ autoreconfHook ];
meta = {
description = "Time command execution over multiple executions";
longDescription = ''
Unix's `time` utility is a simple and often effective way of measuring
how long a command takes to run. 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 (with confidence
intervals), standard deviations, minimums, medians, and maximums having
done so. This can give a much better understanding of the command's
performance.
'';
license = stdenv.lib.licenses.mit;
homepage = "https://tratt.net/laurie/src/multitime/";
platforms = stdenv.lib.platforms.unix;
};
}

View file

@ -5035,6 +5035,8 @@ in
mt-st = callPackage ../tools/backup/mt-st {};
multitime = callPackage ../tools/misc/multitime { };
multitran = recurseIntoAttrs (let callPackage = newScope pkgs.multitran; in {
multitrandata = callPackage ../tools/text/multitran/data { };