nixpkgs/pkgs/tools/text/gawk/default.nix

54 lines
1.7 KiB
Nix
Raw Normal View History

{ stdenv, fetchurl, xz, libsigsegv, readline, interactive ? false }:
* The stdenv setup script now defines a generic builder that allows builders for typical Autoconf-style to be much shorten, e.g., . $stdenv/setup genericBuild The generic builder does lots of stuff automatically: - Unpacks source archives specified by $src or $srcs (it knows about gzip, bzip2, tar, zip, and unpacked source trees). - Determines the source tree. - Applies patches specified by $patches. - Fixes libtool not to search for libraries in /lib etc. - Runs `configure'. - Runs `make'. - Runs `make install'. - Strips debug information from static libraries. - Writes nested log information (in the format accepted by `log2xml'). There are also lots of hooks and variables to customise the generic builder. See `stdenv/generic/docs.txt'. * Adapted the base packages (i.e., the ones used by stdenv) to use the generic builder. * We now use `curl' instead of `wget' to download files in `fetchurl'. * Neither `curl' nor `wget' are part of stdenv. We shouldn't encourage people to download stuff in builders (impure!). * Updated some packages. * `buildinputs' is now `buildInputs' (but the old name also works). * `findInputs' in the setup script now prevents inputs from being processed multiple times (which could happen, e.g., if an input was a propagated input of several other inputs; this caused the size variables like $PATH to blow up exponentially in the worst case). * Patched GNU Make to write nested log information in the format accepted by `log2xml'. Also, prior to writing the build command, Make now writes a line `building X' to indicate what is being built. This is unfortunately often obscured by the gigantic tool invocations in many Makefiles. The actual build commands are marked `unimportant' so that they don't clutter pages generated by `log2html'. svn path=/nixpkgs/trunk/; revision=845
2004-03-19 17:53:04 +01:00
2014-08-27 01:14:09 +02:00
let
inherit (stdenv.lib) optional;
in
2012-09-18 20:50:35 +02:00
stdenv.mkDerivation rec {
2015-03-26 23:13:50 +01:00
name = "gawk-4.1.1";
src = fetchurl {
2012-09-18 20:50:35 +02:00
url = "mirror://gnu/gawk/${name}.tar.xz";
2015-03-26 23:13:50 +01:00
sha256 = "1nz83vpss8xv7m475sv4qhhj40g74nvcw0y9kwq9ds8wzfmcdm7g";
};
2014-08-27 01:14:09 +02:00
# When we do build separate interactive version, it makes sense to always include docs.
outputs = [ "out" ] ++ stdenv.lib.optional (!interactive) "doc"; #ToDo
2015-03-26 23:13:50 +01:00
# Currently broken due to locale tests failing
#doCheck = !stdenv.isCygwin; # XXX: `test-dup2' segfaults on Cygwin 6.1
buildInputs = [ xz.bin libsigsegv ]
2014-08-27 01:14:09 +02:00
++ optional interactive readline;
configureFlags = [ "--with-libsigsegv-prefix=${libsigsegv}" ]
2014-08-27 01:14:09 +02:00
++ [(if interactive then "--with-readline=${readline}" else "--without-readline")];
postInstall = "rm $out/bin/gawk-*";
meta = with stdenv.lib; {
homepage = http://www.gnu.org/software/gawk/;
description = "GNU implementation of the Awk programming language";
longDescription = ''
Many computer users need to manipulate text files: extract and then
operate on data from parts of certain lines while discarding the rest,
make changes in various text files wherever certain patterns appear,
and so on. To write a program to do these things in a language such as
C or Pascal is a time-consuming inconvenience that may take many lines
of code. The job is easy with awk, especially the GNU implementation:
Gawk.
The awk utility interprets a special-purpose programming language that
makes it possible to handle many data-reformatting jobs with just a few
lines of code.
'';
license = licenses.gpl3Plus;
platforms = platforms.unix;
2015-01-13 22:33:24 +01:00
maintainers = [ ];
};
}