include the closure of /bin/sh. Otherwise all builders that call
/bin/sh will fail when using the new chroot implementation, which
only bind-mounts the inputs of a build rather than the whole Nix
store.
svn path=/nixos/trunk/; revision=13640
automatic copying of build results from remote Nix stores work
more-or-less automatically. All you have to do is mount the remote
FS on a subdirectory of /var/run/nix/remote-stores, e.g.
$ sshfs remote_machine:/ /var/run/nix/remote-stores/foo
* Set $NIXPKGS_ALL.
svn path=/nixos/trunk/; revision=12411
by default since this can really make the functioning of
applications unpredictable as they can pick up arbitrary
library versions from that directory. LD_LIBRARY_PATH should only
contain very specific paths (like /var/run/opengl-driver/lib for
overriding the system OpenGL implementation, or the NSS module
path). This is even more important given that the stdenv-updates
branch uses RUNPATHs instead of RPATHs, so *all* libraries are
overridable by LD_LIBRARY_PATH.
svn path=/nixos/trunk/; revision=11967
add `/var/run/current-system/sw/lib' to `LD_LIBRARY_PATH'. This should allow
NSS modules to be added and taken into account by applications without
the need to reboot.
svn path=/nixos/trunk/; revision=11290
Currently, the solution is a bit hackish since running applications
will not work after a `nixos-rebuild' because `libnss_mdns' is not
in their `LD_LIBRARY_PATH'.
svn path=/nixos/trunk/; revision=11162
This variable is not honored by `aclocal' itself but by the wrapper that's
installed for `aclocal' by the `automake' package.
svn path=/nixos/trunk/; revision=10990
of `$EMACSLOADPATH' overrides Emacs's default `load-path', which
contains useful directories like `$EMACS/share/emacs/22.1/lisp',
etc.
svn path=/nixos/trunk/; revision=10792
thanks to unionfs. For instance, nix-env and nixos-rebuild work.
The tricky part was to build a Nix database (in the tmpfs/unionfs)
which is now necessary to prevent store paths on the CD from being
deleted right away because they otherwise wouldn't be valid.
* nixos-install: use the /etc/nixos/configuration.nix from the target
file system (don't copy it anymore). Since the user is supposed to
mount the target file system on /mnt anyway, we may as well require
that configuration.nix is placed in /mnt/etc/nixos. This also makes
upgrading / reinstalling much easier, since it will automatically
use the right configuration.nix.
svn path=/nixos/trunk/; revision=10399
Just set nix.distributedBuilds to true and nix.buildMachines
to a list of machines that can perform Nix builds via SSH,
and local builds will be forwarded appropriately. So now
any user can say something like
nix-build /etc/nixos/nixpkgs/ --arg system '"powerpc-linux"' -A libxml2
and the build for powerpc-linux will be forwarded to a machine
of that type.
svn path=/nixos/trunk/; revision=9696
