packages that we need rather than just /var/run/current-system/sw.
This ensures consistency when upgrading a system (e.g. you don't end
up with a mix of KDE versions at runtime). This partially reverts
r14148 (in particular the update-mime-database hack in the
systemPath post-build).
svn path=/nixos/trunk/; revision=14887
the advantage that KDE applications work when logging in via ssh,
and that you don't need to logout to have KDE upgrades take effect.
On the downside, since the various KDE packages and shared-mime-info
all have their own MIME databases, if we put them in one symlink
tree (systemPath), we need to rerun update-mime-database on the
symlink tree. Also, systemPath is getting very large.
svn path=/nixos/trunk/; revision=14148
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
