about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorFilesLines
2008-12-12 * We can't use string objects in signal handlers because they mightEelco Dolstra1-4/+4
allocate memory, which is verboten in signal handlers. This caused random failures in the test suite on Mac OS X (triggered by the spurious SIGPOLL signals on Mac OS X, which should also be fixed).
2008-12-12 * Use a PathSet for the chroot directories so that we don'tEelco Dolstra1-6/+7
accidentally bind-mount a directory twice.
2008-12-12 * Define _GNU_SOURCE. Hopefully this fixes the build on Debian 4.0Eelco Dolstra1-0/+3
(http://hydra.nixos.org/nixlog/384/1).
2008-12-11 * Don't provide the whole Nix store in the chroot, but only theEelco Dolstra1-10/+44
closure of the inputs. This really enforces that there can't be any undeclared dependencies on paths in the store. This is done by creating a fake Nix store and creating bind-mounts or hard-links in the fake store for all paths in the closure. After the build, the build output is moved from the fake store to the real store. TODO: the chroot has to be on the same filesystem as the Nix store for this to work, but this isn't enforced yet. (I.e. it only works currently if /tmp is on the same FS as /nix/store.)
2008-12-11 * Revert r13150: now that we use private namespaces for the chroot, weEelco Dolstra4-9/+1
don't have to put the chroot in /nix/var/nix/chroots anymore. They're back in /tmp now.
2008-12-11 * Provide a minimal /etc/passwd in the chroot to keep some buildersEelco Dolstra1-1/+12
happy.
2008-12-11 * Do chroot builds in a private namespace. This means that all theEelco Dolstra2-134/+46
bind-mounts we do are only visible to the builder process and its children. So accidentally doing "rm -rf" on the chroot directory won't wipe out /nix/store and other bind-mounted directories anymore. Also, the bind-mounts in the private namespace disappear automatically when the builder exits.
2008-12-11 * Open the connection to the daemon lazily (on demand) so thatEelco Dolstra3-6/+38
read-only operations (like nix-env -qa) work properly when the daemon isn't running.
2008-12-04 * Build on Debian 4.0 (GCC 4.1.1).Eelco Dolstra1-1/+1
2008-12-04 * Doh.Eelco Dolstra1-2/+2
2008-12-04 * Build some 64-bit RPMs/Debs.Eelco Dolstra1-10/+21
2008-12-04 * Be sure to clean up the daemon if the test fails.Eelco Dolstra1-0/+2
2008-12-04 (no commit message)Eelco Dolstra1-2/+1
2008-12-04 * Propagate --max-silent-time to remote machines.Eelco Dolstra2-2/+7
2008-12-04 * Prefer building on a remote machine over a local machine. ThisEelco Dolstra1-5/+6
makes more sense for the build farm, otherwise every nix-store invocation will lead to at least one local build. Will come up with a better solution later...
2008-12-04 * Build RPMs, Debs, coverage analysis.Eelco Dolstra1-50/+154
2008-12-04 * When using build hooks, for any nix-store -r build operation, it isEelco Dolstra2-7/+18
necessary that at least one build hook doesn't return "postpone", otherwise nix-store will barf ("waiting for a build slot, yet there are no running children"). So inform the build hook when this is the case, so that it can start a build even when that would exceed the maximum load on a machine.
2008-12-04 * Force allocation of a pseudo-terminal to clean up the remoteEelco Dolstra1-1/+6
nix-store process when the connection is interrupted.
2008-12-04 * Don't ignore errors from writing to stderr. That way, whenEelco Dolstra1-5/+1
nix-store -r (or some other operation) is started via ssh, it will at least have a chance of terminating quickly when the connection is killed. Right now it just runs to completion, because it never notices that stderr is no longer connected to anything. Of course it would be better if sshd would just send a SIGHUP, but it doesn't (https://bugzilla.mindrot.org/show_bug.cgi?id=396).
2008-12-04 * Support multiple system types per remote machine, e.g. a machineEelco Dolstra1-24/+24
list like root@example.org x86_64-linux /root/.ssh/id_buildfarm 1 root@example.org i686-darwin /root/.ssh/id_buildfarm 1 This is possible when the Nix installation on example.org itself has remote builds enabled.
2008-12-04 (no commit message)Eelco Dolstra1-3/+4
2008-12-04 * Dirty hack to make nix-push work properly on derivations: theEelco Dolstra2-10/+24
derivation should be a source rather than a derivation dependency of the call to the NAR derivation. Otherwise the derivation (and all its dependencies) will be built as a side-effect, which may not even succeed.
2008-12-03 * addToStore() in nix-worker: don't write the NAR dump received fromEelco Dolstra3-25/+85
the client to a temporary directory, as that is highly inefficient.
2008-12-03 * A simple API for parsing NAR archives.Eelco Dolstra3-26/+80
2008-12-03 * Backwards compatibility.Eelco Dolstra1-4/+9
2008-12-03 (no commit message)Eelco Dolstra2-1/+2
2008-12-03 * Pass HashType values instead of strings.Eelco Dolstra11-23/+36
2008-12-03 * Made addToStore() a lot more efficient: it no longer reads the pathEelco Dolstra2-35/+29
being copied 3 times in the worst case. It doesn't run in constant space, but it didn't do that anyway.
2008-12-03 * Unify the treatment of sources copied to the store, and recursiveEelco Dolstra12-79/+191
SHA-256 outputs of fixed-output derivations. I.e. they now produce the same store path: $ nix-store --add x /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x $ nix-store --add-fixed --recursive sha256 x /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x the latter being the same as the path that a derivation derivation { name = "x"; outputHashAlgo = "sha256"; outputHashMode = "recursive"; outputHash = "..."; ... }; produces. This does change the output path for such fixed-output derivations. Fortunately they are quite rare. The most common use is fetchsvn calls with SHA-256 hashes. (There are a handful of those is Nixpkgs, mostly unstable development packages.) * Documented the computation of store paths (in store-api.cc).
2008-11-29 * Install the release notes.Eelco Dolstra2-1/+6
2008-11-26 * Moved the build farm job for building Nix to the Nix tree.Eelco Dolstra3-27/+81
2008-11-25 * Ignore carriage returns.Eelco Dolstra1-0/+1
2008-11-25 * Handle prematurely ended logfiles, i.e. make sure we emit enoughEelco Dolstra1-5/+17
close tags.
2008-11-20 * Bump the version number.Eelco Dolstra1-1/+1
2008-11-20 (no commit message)Eelco Dolstra1-1/+8
2008-11-20 * Urgh.Eelco Dolstra1-1/+1
2008-11-20 (no commit message)Eelco Dolstra1-1/+2
2008-11-20 (no commit message)Eelco Dolstra1-1/+1
2008-11-20 (no commit message)Eelco Dolstra1-2/+1
2008-11-20 * Urgh.Eelco Dolstra9-21/+31
2008-11-20 (no commit message)Eelco Dolstra1-2/+0
2008-11-20 * Blindly doing a replacement of occurences of $bindir (when runningEelco Dolstra1-1/+0
the tests) is a bad idea when $bindir = /usr and some programs (like perl) live there. Fortunately it doesn't seem to be needed anymore.
2008-11-20 * Don't set the prefix to /nix by default, rather use the AutoconfEelco Dolstra3-11/+12
default of /usr/local. However, localstatedir and storedir are set to /nix/var/nix and /nix/store respectively unless they're explicitly overriden.
2008-11-20 * Nix daemon: reload the configuration file after forking (NIX-100).Eelco Dolstra3-1/+14
2008-11-20 (no commit message)Eelco Dolstra1-1/+2
2008-11-19 * Primop builtins.storePath for declaring a store path as aEelco Dolstra2-1/+23
dependency. `storePath /nix/store/bla' gives exactly the same result as `toPath /nix/store/bla', except that the former includes /nix/store/bla in the dependency context of the string. Useful in some generated Nix expressions like nix-push, which now finally does the right thing wrt distributed builds. (Previously the path to be packed wasn't an explicit dependency, so it wouldn't be copied to the remote machine.)
2008-11-19 * Patterns.Eelco Dolstra1-31/+73
2008-11-19 (no commit message)Eelco Dolstra2-1/+62
2008-11-19 * Updated the manual.Eelco Dolstra2-3/+134
2008-11-19 * Files in the info directory starting with "." are temporary filesEelco Dolstra1-2/+5
and don't indicate path validity.