depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2004-06-28	* Added a switch `--fallback'. From the manual:	Eelco Dolstra	1	-2/+5
	Whenever Nix attempts to realise a derivation for which a closure is already known, but this closure cannot be realised, fall back on normalising the derivation. The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository. If the repository is down, the realisation of the derivation will fail. When this option is specified, Nix will build the derivation instead. Thus, binary installation falls back on a source installation. This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
2004-06-21	* Disable calls to fsync() since Berkeley DB's DB_TXN_WRITE_NOSYNC	Eelco Dolstra	1	-0/+8
	flag doesn't seem to work as advertised.
2004-06-20	* Refactoring.	Eelco Dolstra	1	-41/+2

2004-01-15	* Catch SIGINT to terminate cleanly when the user tries to interrupt	Eelco Dolstra	1	-1/+8
	Nix. This is to prevent Berkeley DB from becoming wedged. Unfortunately it is not possible to throw C++ exceptions from a signal handler. In fact, you can't do much of anything except change variables of type `volatile sig_atomic_t'. So we set an interrupt flag in the signal handler and check it at various strategic locations in the code (by calling checkInterrupt()). Since this is unlikely to cover all cases (e.g., (semi-)infinite loops), sometimes SIGTERM may now be required to kill Nix.
2004-01-13	* Periodically checkpoint the log.	Eelco Dolstra	1	-1/+3

2004-01-13	* Tricky: make sure that the accessor count is not reset to 0 if	Eelco Dolstra	1	-1/+5
	recovery fails.
2004-01-07	* Upgraded to Berkeley DB 4.2.52. The main advantage of 4.2 is that	Eelco Dolstra	1	-1/+1
	it automatically removes log files when they are no longer needed. * IMPORTANT * If you have an existing Nix installation, you must checkpoint the Nix database to prevent recent transactions from being undone. Do the following: - optional: make a backup of $prefix/var/nix/db. - run `db_checkpoint' from Berkeley DB 4.1: $ db_checkpoint -h $prefix/var/nix/db -1 - optional (?): run `db_recover' from Berkeley DB 4.1: $ db_recover -h $prefix/var/nix/db - remove $prefix/var/nix/db/log* and $prefix/var/nix/db/__db*
2003-11-19	* nix-env: a tool to manage user environments.	Eelco Dolstra	1	-2/+2
	* Replace all directory reading code by a generic readDirectory() function.
2003-11-18	* libnix -> libstore.	Eelco Dolstra	1	-0/+425