aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-07-17queryPathInfo(): return hash in base-32 if desiredEelco Dolstra
Cherry-picked from the no-manifests branch.
2012-07-17Return an exit code of 100 for cached failed buildsEelco Dolstra
Exit code 100 should be returned for all permanent failures. This includes cached failures. Fixes #34.
2012-07-17Remove dead codeEelco Dolstra
2012-07-17Manual: Don't claim we support CygwinEelco Dolstra
2012-07-17Update Nix 1.1 release notesEelco Dolstra
2012-07-17Allow disabling log compressionEelco Dolstra
2012-07-12builtins.storePath: resolve symlinksEelco Dolstra
Needed for Charon/Hydra interaction.
2012-07-09Pass --insecure to curl so that https worksEelco Dolstra
2012-07-09Inline fetchurl.shEelco Dolstra
2012-07-09Add a test for the fetchurl functionEelco Dolstra
2012-07-09Remove obsolete commentShea Levy
2012-07-09corepkgs/fetchurl: Build locally and outside of the chrootShea Levy
2012-07-09corepkgs/fetchurl: the 'system' argument can be optionalShea Levy
2012-07-09corepkgs: distribute fetchurl filesShea Levy
2012-07-09corepkgs/fetchurl: Call the shell directly instead of using the shebangShea Levy
2012-07-09corepkgs/fetchurl.sh: Use config.nix's curlShea Levy
2012-07-09The fetchurl builder is now fetchurl.shShea Levy
2012-07-09Remove old fetchurl makefileShea Levy
2012-07-09Move fetchurl files out of their subdirectoryShea Levy
2012-07-09corepkgs/config.nix.in: We'll need curlShea Levy
2012-07-09Resurrect old corepkgs fetchurlShea Levy
2012-07-09Really fix RPM buildsEelco Dolstra
2012-07-09Fix RPM buildsEelco Dolstra
http://hydra.nixos.org/build/2784908
2012-07-09Get rid of nix.conf.exampleEelco Dolstra
No need to duplicate the nix.conf manpage.
2012-07-09Install a nix.conf manpageEelco Dolstra
2012-06-27nix-store -r: do substitutions in parallelEelco Dolstra
I.e. when multiple non-derivation arguments are passed to ‘nix-store -r’ to be substituted, do them in parallel.
2012-06-27Mount an empty /dev/shm tmpfs in the chrootEelco Dolstra
This ensures that whatever the builder writes in /dev/shm is automatically cleaned up.
2012-06-27Check the return code of the clone() callEelco Dolstra
2012-06-25When using chroots, use a private PID namespaceEelco Dolstra
In a private PID namespace, processes have PIDs that are separate from the rest of the system. The initial child gets PID 1. Processes in the chroot cannot see processes outside of the chroot. This improves isolation between builds. However, processes on the outside can see processes in the chroot and send signals to them (if they have appropriate rights). Since the builder gets PID 1, it serves as the reaper for zombies in the chroot. This might turn out to be a problem. In that case we'll need to have a small PID 1 process that sits in a loop calling wait().
2012-06-25Use a private UTS namespace to provide a deterministic host/domain name to ↵Eelco Dolstra
builders In chroot builds, set the host name to "localhost" and the domain name to "(none)" (the latter being the kernel's default). This improves determinism a bit further. P.S. I have to idea what UTS stands for.
2012-06-23Update release notesEelco Dolstra
2012-06-23Improve error messageEelco Dolstra
2012-06-23In chroot builds, use a private SysV IPC namespaceEelco Dolstra
This improves isolation a bit further, and it's just one extra flag in the unshare() call. P.S. It would be very cool to use CLONE_NEWPID (to put the builder in a private PID namespace) as well, but that's slightly more risky since having a builder start as PID 1 may cause problems.
2012-06-23In chroot builds, use a private network namespaceEelco Dolstra
On Linux it's possible to run a process in its own network namespace, meaning that it gets its own set of network interfaces, disjunct from the rest of the system. We use this to completely remove network access to chroot builds, except that they get a private loopback interface. This means that: - Builders cannot connect to the outside network or to other processes on the same machine, except processes within the same build. - Vice versa, other processes cannot connect to processes in a chroot build, and open ports/connections do not show up in "netstat". - If two concurrent builders try to listen on the same port (e.g. as part of a test), they no longer conflict with each other. This was inspired by the "PrivateNetwork" flag in systemd.
2012-06-18Support socket-based, on-demand activation of the Nix daemon with systemdEelco Dolstra
Systemd can start the Nix daemon on demand when the Nix daemon socket is first accessed. This is signalled through the LISTEN_FDS environment variable, so all we need to do is check for that and then use file descriptor 3 as the listen socket instead of creating one ourselves.
2012-05-31Add Emacs to the disk imageEelco Dolstra
2012-05-31fixes to nix-worker systemd service descriptor: - remove commented-out lines ↵Michel Alexandre Salim
- register the file for distribution in Makefile.am
2012-05-31On systems with SystemD, install the service descriptor for nix-worker, and ↵Michel Alexandre Salim
enable and start it
2012-05-31Major spec update: - Fix license field - Split into subpackages - Update ↵Michel Alexandre Salim
build dependencies - Configure users and groups for multi-user mode - Fix installation location of Perl modules
2012-05-31Update nix profile: - incorporate NixOS's configuration so that nix is ↵Michel Alexandre Salim
usable by normal users - install as a data file, not a program file
2012-05-31- only enable deprecated spec sections when building on systems with older ↵Michel Alexandre Salim
RPM versions - move tests to dedicated %check section - use standard build macros
2012-05-31- replace %define with %globalMichel Alexandre Salim
2012-05-30Compress build logs on the fly using bzip2Eelco Dolstra
2012-05-30"nix-store -l": support compressed logsEelco Dolstra
2012-05-29Reserve some disk space for the garbage collectorEelco Dolstra
We can't open a SQLite database if the disk is full. Since this prevents the garbage collector from running when it's most needed, we reserve some dummy space that we can free just before doing a garbage collection. This actually revives some old code from the Berkeley DB days. Fixes #27.
2012-05-29Add option ‘build-keep-log’ to enable/disable writing of build logsEelco Dolstra
Fixes #26.
2012-05-24Clean up the installation section; document the generic binary tarballsEelco Dolstra
2012-05-22Fix owner/group in tar invocationEelco Dolstra
2012-05-22Generate binary tarballs for installing NixEelco Dolstra
For several platforms we don't currently have "native" Nix packages (e.g. Mac OS X and FreeBSD). This provides the next best thing: a tarball containing the closure of Nix, plus a simple script "nix-finish-install" that initialises the Nix database, registers the paths in the closure as valid, and runs "nix-env -i /path/to/nix" to initialise the user profile. The tarball must be unpacked in the root directory. It creates /nix/store/... and /usr/bin/nix-finish-install. Typical installation is as follows: $ cd / $ tar xvf /path/to/nix-1.1pre1234_abcdef-x86_64-linux.tar.bz2 $ nix-finish-install (if necessary add ~/.nix-profile/etc/profile.d/nix.sh to the shell login scripts) After this, /usr/bin/nix-finish-install can be deleted, if desired. The downside to the binary tarball is that it's pretty big (~55 MiB for x86_64-linux).
2012-05-22Remove $FONTCONFIG_FILE hack from nix-profile.shEelco Dolstra
It's no longer needed because Nixpkgs' fontconfig uses /etc/fonts/fonts.conf as a default, just like other distributions.