1 { fetchurl, lib, stdenv, emacs, gnulib, autoconf, bison, automake, gettext, gperf, texinfo, perl, rsync}:
3 stdenv.mkDerivation rec {
8 url = "mirror://gnu/idutils/idutils-${version}.tar.xz";
9 sha256 = "1hmai3422iaqnp34kkzxdnywl7n7pvlxp11vrw66ybxn9wxg90c1";
13 # replace embedded gnulib tests with those from gnulib package
14 bash -O extglob -c "cd gnulib-tests; rm -r !(Makefile.am)"
15 substituteInPlace ./configure.ac --replace "AC_PREREQ(2.61)" "AC_PREREQ(2.64)"
16 ./bootstrap --force --gnulib-srcdir=${gnulib} --skip-po --bootstrap-sync --no-git
19 buildInputs = lib.optional stdenv.isLinux emacs;
20 nativeBuildInputs = [ gnulib autoconf bison automake gettext gperf texinfo perl rsync ];
22 doCheck = !stdenv.isDarwin;
24 patches = [ ./nix-mapping.patch ];
27 description = "Text searching utility";
30 An "ID database" is a binary file containing a list of file
31 names, a list of tokens, and a sparse matrix indicating which
32 tokens appear in which files.
34 With this database and some tools to query it, many
35 text-searching tasks become simpler and faster. For example,
36 you can list all files that reference a particular `\#include'
37 file throughout a huge source hierarchy, search for all the
38 memos containing references to a project, or automatically
39 invoke an editor on all files containing references to some
40 function or variable. Anyone with a large software project to
41 maintain, or a large set of text files to organize, can benefit
42 from the ID utilities.
44 Although the name `ID' is short for `identifier', the ID
45 utilities handle more than just identifiers; they also treat
46 other kinds of tokens, most notably numeric constants, and the
47 contents of certain character strings.
50 homepage = "https://www.gnu.org/software/idutils/";
51 license = licenses.gpl3Plus;
53 maintainers = with maintainers; [ gfrascadorio ];
54 platforms = lib.platforms.all;