2012-03-03 09:52:55 +00:00
|
|
|
{stdenv, fetchurl, withMan ? false, help2man ? null}:
|
* 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 16:53:04 +00:00
|
|
|
|
2012-03-03 09:52:55 +00:00
|
|
|
assert withMan -> help2man != null;
|
|
|
|
|
|
|
|
stdenv.mkDerivation (rec {
|
2010-12-12 23:35:27 +00:00
|
|
|
name = "gnutar-1.25";
|
2010-04-23 09:11:23 +00:00
|
|
|
|
2003-11-03 10:22:00 +00:00
|
|
|
src = fetchurl {
|
2010-12-12 23:35:27 +00:00
|
|
|
url = "mirror://gnu/tar/tar-1.25.tar.bz2";
|
|
|
|
sha256 = "0js9b1jd93kjk6dgf40y2fpgpnix247rk5aws2mjgwz0p10wxxpk";
|
2003-11-03 10:22:00 +00:00
|
|
|
};
|
2008-02-06 13:18:50 +00:00
|
|
|
|
|
|
|
meta = {
|
2009-03-07 11:35:18 +00:00
|
|
|
homepage = http://www.gnu.org/software/tar/;
|
|
|
|
description = "GNU implementation of the `tar' archiver";
|
|
|
|
|
|
|
|
longDescription = ''
|
|
|
|
The Tar program provides the ability to create tar archives, as
|
|
|
|
well as various other kinds of manipulation. For example, you
|
|
|
|
can use Tar on previously created archives to extract files, to
|
|
|
|
store additional files, or to update or list files which were
|
|
|
|
already stored.
|
|
|
|
|
|
|
|
Initially, tar archives were used to store files conveniently on
|
|
|
|
magnetic tape. The name "Tar" comes from this use; it stands
|
|
|
|
for tape archiver. Despite the utility's name, Tar can direct
|
|
|
|
its output to available devices, files, or other programs (using
|
|
|
|
pipes), it can even access remote devices or files (as
|
|
|
|
archives).
|
|
|
|
'';
|
|
|
|
|
|
|
|
license = "GPLv3+";
|
2010-04-23 09:11:23 +00:00
|
|
|
|
|
|
|
maintainers = [ stdenv.lib.maintainers.ludo ];
|
|
|
|
platforms = stdenv.lib.platforms.all;
|
2008-02-06 13:18:50 +00:00
|
|
|
};
|
2012-03-03 09:52:55 +00:00
|
|
|
} // (if withMan then {
|
|
|
|
buildInputs = [ help2man ];
|
|
|
|
postInstall = ''
|
|
|
|
ensureDir $out/share/man/man1
|
|
|
|
help2man $out/bin/tar > $out/share/man/man1/tar.1
|
|
|
|
'';
|
|
|
|
} else {}))
|