about summary refs log tree commit diff
path: root/corepkgs
AgeCommit message (Collapse)AuthorFilesLines
2014-08-20 Use proper quotes everywhereEelco Dolstra1-9/+9
2014-07-16 Pass *_proxy vars to bootstrap fetchurlShea Levy1-0/+8
2014-04-04 derivation: Don't require certain function argumentsEelco Dolstra1-1/+1
Turns out that in Nixpkgs, derivation is actually called without a ‘name’ argument in some places :-(
2014-04-04 Pass position information to primop callsEelco Dolstra1-1/+1
For example: error: `tail' called on an empty list, at /home/eelco/Dev/nixpkgs/pkgs/applications/misc/hello/ex-2/default.nix:13:7
2014-02-01 Remove AutomakefilesEelco Dolstra1-12/+0
2014-02-01 Update Makefile variable namesEelco Dolstra1-1/+1
2014-01-30 Rename Makefile -> local.mkEelco Dolstra1-0/+0
2013-11-25 Add support for ‘make installcheck’Eelco Dolstra1-1/+1
2013-11-25 Rename Makefile.new -> MakefileEelco Dolstra1-0/+0
2013-11-25 Add a Makefile for the scripts directoryEelco Dolstra1-1/+1
2013-11-25 Add a function for instantiating Autoconf *.in filesEelco Dolstra1-0/+2
2013-11-25 Add a generic rule for installing filesEelco Dolstra1-0/+3
2013-09-02 Lower xz compression levelEelco Dolstra1-1/+1
Fixes #84.
2013-08-26 Fix typos, especially those that end up in the Nix manualIvan Kozik1-2/+2
2013-08-14 corepkgs/nar.nix: Prefer local buildsShea Levy1-0/+3
nar.nix's builder depends on coreutils and nix itself being in $PATH. Unfortunately, there's no good way to ensure that these packages exist in the same place on the remote machine: The local machine may have nix installed in /usr, and the remote machine in /usr/local, but the generated nar.sh builder will refer to /usr and thus fail on the remote machine. This ensures that nar.sh is run on the same machine that instantiates it. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-23 buildenv: remove special treatment of python filesFlorian Friesdorf1-3/+0
buildPythonPackage does not leave easy_install.pth and site.py anymore. A python package that leaves these files is broken. An exception to this is setuptoolsSite which packages setuptools' site.py. To include it into a buildenv, this patch is even needed, not just cosmetic.
2013-07-12 Fix syntax error in unpack-channelEelco Dolstra1-1/+1
2013-07-12 Add gzip support for channel unpackingGergely Risko2-2/+6
2013-07-01 Add support for uncompressed NARs in binary cachesEelco Dolstra1-8/+11
Issue NixOS/hydra#102.
2013-03-08 Revert "Prevent config.h from being clobbered"Eelco Dolstra1-3/+4
This reverts commit 28bba8c44f484eae38e8a15dcec73cfa999156f6.
2013-03-07 Prevent config.h from being clobberedEelco Dolstra1-4/+3
2013-01-21 corepkgs/fetchurl: Enable making the downloaded file executableShea Levy1-3/+4
2012-12-05 Support xz compression of nixexprs.tar in channelsEelco Dolstra1-1/+6
2012-12-04 buildenv.pl: Create symlinks in priority orderEelco Dolstra1-9/+12
This reduces unnecessary symlink/unlink steps.
2012-12-04 Add a test for ‘nix-env --set-flag active ...’Eelco Dolstra2-2/+2
2012-12-04 nix-env: Install all outputs of a derivationEelco Dolstra2-22/+25
If you explicitly install a package, presumably you want all of it. So symlink all outputs in the user environment.
2012-11-26 Make "nix-build -A <derivation>.<output>" do the right thingEelco Dolstra1-3/+3
For example, given a derivation with outputs "out", "man" and "bin": $ nix-build -A pkg produces ./result pointing to the "out" output; $ nix-build -A pkg.man produces ./result-man pointing to the "man" output; $ nix-build -A pkg.all produces ./result, ./result-man and ./result-bin; $ nix-build -A pkg.all -A pkg2 produces ./result, ./result-man, ./result-bin and ./result-2.
2012-09-11 Don't use -warning=no-timestamp unless we have GNU tarEelco Dolstra1-1/+1
http://hydra.nixos.org/build/2998485
2012-08-01 nix-channel: Use binary caches advertised by channelsEelco Dolstra1-3/+7
Channels can now advertise a binary cache by creating a file <channel-url>/binary-cache-url. The channel unpacker puts these in its "binary-caches" subdirectory. Thus, the URLS of the binary caches for the channels added by root appear in /nix/var/nix/profiles/per-user/eelco/channels/binary-caches/*. The binary cache substituter reads these and adds them to the list of binary caches.
2012-08-01 Use a GNU tar flag to shut up warnings about implausibly old timestampEelco Dolstra2-1/+2
2012-08-01 Inline unpack-channel.shEelco Dolstra3-8/+17
2012-07-26 Merge branch 'master' into no-manifestsEelco Dolstra2-1/+23
2012-07-25 import: If the path is a valid .drv file, parse it and generate a derivation ↵Shea Levy2-1/+23
attrset. The generated attrset has drvPath and outPath with the right string context, type 'derivation', outputName with the right name, all with a list of outputs, and an attribute for each output. I see three uses for this (though certainly there may be more): * Using derivations generated by something besides nix-instantiate (e.g. guix) * Allowing packages provided by channels to be used in nix expressions. If a channel installed a valid deriver for each package it provides into the store, then those could be imported and used as dependencies or installed in environment.systemPackages, for example. * Enable hydra to be consistent in how it treats inputs that are outputs of another build. Right now, if an input is passed as an argument to the job, it is passed as a derivation, but if it is accessed via NIX_PATH (i.e. through the <> syntax), then it is a path that can be imported. This is problematic because the build being depended upon may have been built with non-obvious arguments passed to its jobset file. With this feature, hydra can just set the name of that input to the path to its drv file in NIX_PATH
2012-07-11 Merge branch 'master' of github.com:NixOS/nix into no-manifestsEelco Dolstra3-1/+38
2012-07-09 Pass --insecure to curl so that https worksEelco Dolstra1-1/+1
2012-07-09 Inline fetchurl.shEelco Dolstra3-9/+13
2012-07-09 Remove obsolete commentShea Levy1-3/+0
2012-07-09 corepkgs/fetchurl: Build locally and outside of the chrootShea Levy1-0/+6
2012-07-09 corepkgs/fetchurl: the 'system' argument can be optionalShea Levy1-1/+1
2012-07-09 corepkgs: distribute fetchurl filesShea Levy1-1/+1
2012-07-09 corepkgs/fetchurl: Call the shell directly instead of using the shebangShea Levy2-3/+2
2012-07-09 corepkgs/fetchurl.sh: Use config.nix's curlShea Levy2-2/+4
2012-07-09 The fetchurl builder is now fetchurl.shShea Levy1-1/+1
2012-07-09 Remove old fetchurl makefileShea Levy1-11/+0
2012-07-09 Move fetchurl files out of their subdirectoryShea Levy2-0/+0
2012-07-09 corepkgs/config.nix.in: We'll need curlShea Levy1-0/+1
2012-07-09 Resurrect old corepkgs fetchurlShea Levy3-0/+39
2012-07-01 Fix xz compressionEelco Dolstra1-3/+3
2012-07-01 Allow both bzip2 and xz compressionEelco Dolstra1-5/+13
2012-06-29 Use XZ compression in binary cachesEelco Dolstra2-5/+7
XZ compresses significantly better than bzip2. Here are the compression ratios and execution times (using 4 cores in parallel) on my /var/run/current-system (3.1 GiB): bzip2: total compressed size 849.56 MiB, 30.8% [2m08] xz -6: total compressed size 641.84 MiB, 23.4% [6m53] xz -7: total compressed size 621.82 MiB, 22.6% [7m19] xz -8: total compressed size 599.33 MiB, 21.8% [7m18] xz -9: total compressed size 588.18 MiB, 21.4% [7m40] Note that compression takes much longer. More importantly, however, decompression is much faster: bzip2: 1m47.274s xz -6: 0m55.446s xz -7: 0m54.119s xz -8: 0m52.388s xz -9: 0m51.842s The only downside to using -9 is that decompression takes a fair amount (~65 MB) of memory.