3
0
Fork 0
forked from mirrors/nixpkgs
nixpkgs/pkgs/development/tools/misc/coccinelle/default.nix
Bjørn Forsman c9baba9212 Fix many package descriptions
(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.
2014-08-24 22:31:37 +02:00

63 lines
2.1 KiB
Nix

{ fetchurl, stdenv, python, ncurses, ocamlPackages, pkgconfig, makeWrapper }:
let
name = "coccinelle-1.0.0-rc15";
sha256 = "07fab4e17512925b958890bb13c0809797074f2e44a1107b0074bdcc156b9596";
in stdenv.mkDerivation {
inherit name;
src = fetchurl {
url = "http://coccinelle.lip6.fr/distrib/${name}.tgz";
inherit sha256;
};
buildInputs = with ocamlPackages; [
ocaml findlib menhir
ocaml_pcre pycaml
python ncurses pkgconfig
makeWrapper
];
# TODO: is the generation of this wrapper truly/still needed?
# I don't have a non-NixOS system, so I cannot verify this, but shouldn't
# libpython know where to find its modules? (the path is for example in
# its Sys-module).
postInstall =
# On non-NixOS systems, Coccinelle would end up looking up Python modules
# in the wrong directory.
'' for p in "$out/bin/"*
do
wrapProgram "$p" \
--prefix "PYTHONPATH" ":" "${python}/lib/python${python.majorVersion}"
done
'';
configureFlags = "--enable-release";
meta = {
description = "Program to apply semantic patches to C code";
longDescription =
'' Coccinelle is a program matching and transformation engine which
provides the language SmPL (Semantic Patch Language) for specifying
desired matches and transformations in C code. Coccinelle was
initially targeted towards performing collateral evolutions in
Linux. Such evolutions comprise the changes that are needed in
client code in response to evolutions in library APIs, and may
include modifications such as renaming a function, adding a function
argument whose value is somehow context-dependent, and reorganizing
a data structure. Beyond collateral evolutions, Coccinelle is
successfully used (by us and others) for finding and fixing bugs in
systems code.
'';
homepage = http://coccinelle.lip6.fr/;
license = stdenv.lib.licenses.gpl2;
maintainers = [ ];
platforms = stdenv.lib.platforms.gnu; # arbitrary choice
};
}