c9baba9212
(My OCD kicked in today...) Remove repeated package names, capitalize first word, remove trailing periods and move overlong descriptions to longDescription. I also simplified some descriptions as well, when they were particularly long or technical, often based on Arch Linux' package descriptions. I've tried to stay away from generated expressions (and I think I succeeded). Some specifics worth mentioning: * cron, has "Vixie Cron" in its description. The "Vixie" part is not mentioned anywhere else. I kept it in a parenthesis at the end of the description. * ctags description started with "Exuberant Ctags ...", and the "exuberant" part is not mentioned elsewhere. Kept it in a parenthesis at the end of description. * nix has the description "The Nix Deployment System". Since that doesn't really say much what it is/does (especially after removing the package name!), I changed that to "Powerful package manager that makes package management reliable and reproducible" (borrowed from nixos.org). * Tons of "GNU Foo, Foo is a [the important bits]" descriptions is changed to just [the important bits]. If the package name doesn't contain GNU I don't think it's needed to say it in the description either.
51 lines
1.6 KiB
Nix
51 lines
1.6 KiB
Nix
{ fetchurl, stdenv, perl }:
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "parallel-20140222";
|
|
|
|
src = fetchurl {
|
|
url = "mirror://gnu/parallel/${name}.tar.bz2";
|
|
sha256 = "0zb3hg92br6a53jn0pzfl16ffc1hfw81jk7nzw5spkshsdrcqx3y";
|
|
};
|
|
|
|
patchPhase =
|
|
'' sed -i "src/parallel" -e's|/usr/bin/perl|${perl}/bin/perl|g'
|
|
'';
|
|
|
|
preBuild =
|
|
# The `sem' program wants to write to `~/.parallel'.
|
|
'' export HOME="$PWD"
|
|
'';
|
|
|
|
buildInputs = [ perl ];
|
|
doCheck = true;
|
|
|
|
meta = {
|
|
description = "Shell tool for executing jobs in parallel";
|
|
|
|
longDescription =
|
|
'' GNU Parallel is a shell tool for executing jobs in parallel. A job
|
|
is typically a single command or a small script that has to be run
|
|
for each of the lines in the input. The typical input is a list of
|
|
files, a list of hosts, a list of users, or a list of tables.
|
|
|
|
If you use xargs today you will find GNU Parallel very easy to use.
|
|
If you write loops in shell, you will find GNU Parallel may be able
|
|
to replace most of the loops and make them run faster by running
|
|
jobs in parallel. If you use ppss or pexec you will find GNU
|
|
Parallel will often make the command easier to read.
|
|
|
|
GNU Parallel makes sure output from the commands is the same output
|
|
as you would get had you run the commands sequentially. This makes
|
|
it possible to use output from GNU Parallel as input for other
|
|
programs.
|
|
'';
|
|
|
|
homepage = http://www.gnu.org/software/parallel/;
|
|
|
|
license = stdenv.lib.licenses.gpl3Plus;
|
|
|
|
platforms = stdenv.lib.platforms.all;
|
|
maintainers = [ ];
|
|
};
|
|
}
|