Silvan Mosberger 4f0dadbf38 treewide: format all inactive Nix files
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.

Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.

A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.

This commit was automatically created and can be verified using

    nix-build a08b3a4d19.tar.gz \
      --argstr baseRev b32a0943687d2a5094a6d92f25a4b6e16a76b5b7
    result/bin/apply-formatting $NIXPKGS_PATH
2024-12-10 20:26:33 +01:00

46 lines
1.4 KiB
Nix

{
lib,
stdenv,
fetchFromGitHub,
autoreconfHook,
}:
stdenv.mkDerivation rec {
pname = "multitime";
version = "1.4";
src = fetchFromGitHub {
owner = "ltratt";
repo = "multitime";
rev = "multitime-${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 = lib.licenses.mit;
homepage = "https://tratt.net/laurie/src/multitime/";
platforms = lib.platforms.unix;
mainProgram = "multitime";
};
}