depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2014-02-26	Installer: Handle Darwin	Eelco Dolstra	1	-1/+1
	"cp -r" doesn't copy symlinks properly on Darwin, but "cp -R" does. Fixes #215.
2014-02-10	Force use of Bash	Eelco Dolstra	1	-1/+1
	"echo -n" doesn't work with /bin/sh on Darwin.
2014-02-10	Binary tarball: Automatically create /nix	Eelco Dolstra	1	-17/+94
	The tarball can now be unpacked anywhere. The installation script uses "sudo" to create /nix if it doesn't exist. It also fetches the nixpkgs-unstable channel.
2014-02-10	Binary tarball: Automatically fetch the Nixpkgs channel	Eelco Dolstra	1	-1/+7

2012-05-22	Generate binary tarballs for installing Nix	Eelco Dolstra	1	-0/+34
	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).