nixpkgs/pkgs/tools/archivers/gnutar/default.nix

74 lines
2.5 KiB
Nix
Raw Normal View History

2021-01-15 09:19:50 +00:00
{ lib, stdenv, fetchurl, autoreconfHook, acl }:
* 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
# Note: this package is used for bootstrapping fetchurl, and thus
# cannot use fetchpatch! All mutable patches (generated by GitHub or
# cgit) that are needed here should be included directly in Nixpkgs as
# files.
2012-09-18 18:51:15 +00:00
stdenv.mkDerivation rec {
pname = "gnutar";
2021-03-09 23:22:01 +00:00
version = "1.34";
src = fetchurl {
2016-05-19 19:10:55 +00:00
url = "mirror://gnu/tar/tar-${version}.tar.xz";
2021-03-09 23:22:01 +00:00
sha256 = "sha256-Y769JoecXh7qQ1Lw0DyZH5Zq6z3es8dEXJAlaNVBHSg=";
};
2015-06-12 00:58:26 +00:00
# avoid retaining reference to CF during stdenv bootstrap
2021-01-15 09:19:50 +00:00
configureFlags = lib.optionals stdenv.isDarwin [
2015-06-12 00:58:26 +00:00
"gt_cv_func_CFPreferencesCopyAppValue=no"
"gt_cv_func_CFLocaleCopyCurrent=no"
"gt_cv_func_CFLocaleCopyPreferredLanguages=no"
2015-06-12 00:58:26 +00:00
];
# gnutar tries to call into gettext between `fork` and `exec`,
# which is not safe on darwin.
# see http://article.gmane.org/gmane.os.macosx.fink.devel/21882
2021-01-15 09:19:50 +00:00
postPatch = lib.optionalString stdenv.isDarwin ''
substituteInPlace src/system.c --replace '_(' 'N_('
'';
2014-08-26 23:14:09 +00:00
outputs = [ "out" "info" ];
nativeBuildInputs = lib.optional stdenv.isDarwin autoreconfHook;
buildInputs = lib.optional stdenv.isLinux acl;
2014-08-26 23:14:09 +00:00
2012-09-18 18:51:15 +00:00
# May have some issues with root compilation because the bootstrap tool
# cannot be used as a login shell for now.
2021-01-15 09:19:50 +00:00
FORCE_UNSAFE_CONFIGURE = lib.optionalString (stdenv.hostPlatform.system == "armv7l-linux" || stdenv.isSunOS) "1";
2012-09-18 18:51:15 +00:00
2014-10-16 00:52:47 +00:00
preConfigure = if stdenv.isCygwin then ''
sed -i gnu/fpending.h -e 's,include <stdio_ext.h>,,'
'' else null;
doCheck = false; # fails
doInstallCheck = false; # fails
meta = {
homepage = "https://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).
'';
2021-01-15 09:19:50 +00:00
license = lib.licenses.gpl3Plus;
2013-08-16 21:44:33 +00:00
maintainers = [ ];
2021-01-15 09:19:50 +00:00
platforms = lib.platforms.all;
2019-02-19 02:11:16 +00:00
priority = 10;
};
}