mirror of
https://github.com/ilyakooo0/nixpkgs.git
synced 2024-09-28 08:07:24 +03:00
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.
42 lines
1.3 KiB
Nix
42 lines
1.3 KiB
Nix
{ stdenv, fetchurl, m4, perl }:
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "bison-2.7";
|
|
|
|
src = fetchurl {
|
|
url = "mirror://gnu/bison/${name}.tar.gz";
|
|
sha256 = "0cd8s2g7zjshya7kwjc9rh3drsssl4hiq4sccnkgf0nn9wvygfqr";
|
|
};
|
|
|
|
nativeBuildInputs = [ m4 ] ++ stdenv.lib.optional doCheck perl;
|
|
propagatedBuildInputs = [ m4 ];
|
|
|
|
doCheck = true;
|
|
# M4 = "${m4}/bin/m4";
|
|
|
|
meta = {
|
|
homepage = "http://www.gnu.org/software/bison/";
|
|
description = "Yacc-compatible parser generator";
|
|
license = stdenv.lib.licenses.gpl3Plus;
|
|
|
|
longDescription = ''
|
|
Bison is a general-purpose parser generator that converts an
|
|
annotated context-free grammar into an LALR(1) or GLR parser for
|
|
that grammar. Once you are proficient with Bison, you can use
|
|
it to develop a wide range of language parsers, from those used
|
|
in simple desk calculators to complex programming languages.
|
|
|
|
Bison is upward compatible with Yacc: all properly-written Yacc
|
|
grammars ought to work with Bison with no change. Anyone
|
|
familiar with Yacc should be able to use Bison with little
|
|
trouble. You need to be fluent in C or C++ programming in order
|
|
to use Bison.
|
|
'';
|
|
|
|
maintainers = [ stdenv.lib.maintainers.simons ];
|
|
platforms = stdenv.lib.platforms.unix;
|
|
};
|
|
|
|
passthru = { glrSupport = true; };
|
|
}
|