depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2004-08-11	* The predecessor of a successor need not be present. This in	Eelco Dolstra	1	-4/+6
	particular happens on distributed builds or when using push/pull.
2004-08-05	* Clean up the temporary directory for hook communication (and don't	Eelco Dolstra	1	-0/+1
	print out incorrect "build failed" messages).
2004-08-04	* Every real language has a `map' function.	Eelco Dolstra	2	-2/+19

2004-08-04	* Allow primops with more that 1 arguments.	Eelco Dolstra	7	-104/+102

2004-08-04	* Creating a file nix-support/no-scan in the output path of a	Eelco Dolstra	2	-3/+6
	derivation disables scanning for dependencies. Use at your own risk. This is a quick hack to speed up UML image generation (image are very big, say 1 GB). It would be better if the scanner were faster, and didn't read the whole file into memory.
2004-07-06	* Fixed format string error.	Eelco Dolstra	1	-1/+1

2004-07-01	* Don't go into a (sometimes infinite) loop calling the build hook.	Eelco Dolstra	1	-16/+24

2004-07-01	* Nix-instantiate now accepts sets of derivations (just like nix-env).	Eelco Dolstra	1	-0/+9

2004-07-01	* Nix-env operations now by default filter out any derivations for	Eelco Dolstra	1	-9/+28
	system types other than the current system. I.e., `nix-env -i' won't install derivations for other system types, and `nix-env -q' won't show them. The flag `--system-filter SYSTEM' can be used to override the system type used for filtering (but not for building!). The value `*' can be used not to filter anything.
2004-07-01	* Align the columns in the output of `nix-env -q'.	Eelco Dolstra	1	-4/+36

2004-07-01	* Allow the system attribute of derivations to be queried in	Eelco Dolstra	1	-37/+50
	`nix-env -q'. * Queries can now be combined, e.g., `nix-env -q --status --system'.
2004-07-01	* Include some missing headers.	Eelco Dolstra	2	-0/+2

2004-06-29	* Write build logs to disk again.	Eelco Dolstra	1	-1/+29

2004-06-28	* By default, `nix-env -i' now deletes previously installed	Eelco Dolstra	1	-3/+21
	derivations with names matching the derivations being installed. The option `--preserve-installed / -P' overrides this behaviour.
2004-06-28	* In a realisation goal, check the result of the corresponding	Eelco Dolstra	1	-0/+6
	normalisation goal.
2004-06-28	* `nix-env -u' now allows a specific version to be specified when	Eelco Dolstra	1	-4/+7
	upgrading. This fixes a bug reported by Martin: $ nix-env -i foo-1.0 $ nix-env -u foo-1.0 upgrading foo-1.0 to foo-1.1
2004-06-28	* Added a switch `--fallback'. From the manual:	Eelco Dolstra	11	-54/+154
	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-25	* A flag `--keep-going / -k' to keep building goals if one fails, as	Eelco Dolstra	5	-139/+167
	much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags.
2004-06-25	* Don't throw an exception when a build fails. Just terminate the	Eelco Dolstra	1	-58/+214
	goal and allow the problem to be handled elsewhere (e.g., at top-level).
2004-06-24	* Obsolete.	Eelco Dolstra	1	-162/+0

2004-06-24	* Multiple and/or failing substitutes now work.	Eelco Dolstra	1	-12/+42

2004-06-22	* Arghhhhhh	Eelco Dolstra	1	-1/+1

2004-06-22	* Some more diagnostics changes.	Eelco Dolstra	2	-25/+41

2004-06-22	* Well, it's better than printf.	Eelco Dolstra	1	-1/+1

2004-06-22	* Started making Nix's diagnostic messages a bit more useful.	Eelco Dolstra	1	-10/+26

2004-06-22	* Put WEXITSTATUS stuff somewhere else.	Eelco Dolstra	4	-3/+11

2004-06-22	* Reduce gratuitous cut & pasting.	Eelco Dolstra	1	-68/+55

2004-06-22	* Wrapper class around pids.	Eelco Dolstra	4	-87/+162

2004-06-22	* Substitutes should occupy a build slot.	Eelco Dolstra	1	-1/+15

2004-06-22	* Refactoring.	Eelco Dolstra	4	-20/+25

2004-06-21	* Remove debug output.	Eelco Dolstra	1	-1/+0

2004-06-21	* Acquire a lock on the output path when running a substitute. Also	Eelco Dolstra	1	-0/+22
	delete obstructing invalid paths.
2004-06-21	* Ugh, nasty Heisenbug due to an uninitialiased variable. The bug	Eelco Dolstra	1	-0/+1
	only caused a crash if the program was not invoked with a high verbosity level.
2004-06-21	* Remove obstructing invalid store paths add[Text]ToStore().	Eelco Dolstra	1	-0/+6

2004-06-21	* Wrap calls to registerSubstitute() in a single transaction to	Eelco Dolstra	3	-11/+13
	improve throughput. * Don't build the `substitute-rev' table for now, since it caused Theta(N^2) time and log file consumption when adding N substitutes. Maybe we can do without it.
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	* Re-enable support for substitutes in the normaliser.	Eelco Dolstra	5	-107/+383
	* A better substitute mechanism. Instead of generating a store expression for each store path for which we have a substitute, we can have a single store expression that builds a generic program that is invoked to build the desired store path, which is passed as an argument. This means that operations like `nix-pull' only produce O(1) files instead of O(N) files in the store when registering N substitutes. (It consumes O(N) database storage, of course, but that's not a performance problem). * Added a test for the substitute mechanism. * `nix-store --substitute' reads the substitutes from standard input, instead of from the command line. This prevents us from running into the kernel's limit on command line length.
2004-06-20	* Refactoring.	Eelco Dolstra	3	-41/+52

2004-06-19	* Re-enable build hooks.	Eelco Dolstra	1	-72/+325

2004-06-18	* Big refactoring. Move to a much more explicitly state machine based	Eelco Dolstra	3	-764/+869
	approach. This makes it much easier to add extra complexity in the normaliser / realiser (e.g., build hooks, substitutes).
2004-06-18	* This is also useful.	Eelco Dolstra	3	-1/+263

2004-06-18	* Shared (garbage collecting) pointers. Copied from Boost.	Eelco Dolstra	12	-17/+1268

2004-06-15	* Refactoring.	Eelco Dolstra	3	-83/+57

2004-06-08	* Cleanup.	Eelco Dolstra	1	-10/+17

2004-05-18	* Drain the output of the build hook to show error messages. Ugly	Eelco Dolstra	1	-4/+26
	hack.
2004-05-18	* setpgrp() is not POSIX (and on Mac OS X it's different than on	Eelco Dolstra	1	-1/+1
	Linux), so use setpgid().
2004-05-14	* execl() requires a terminating 0.	Eelco Dolstra	1	-10/+21
	* When a fast build wakes up a goal, try to start that goal in the same iteration of the startBuild() loop of run(). Otherwise no job might be started until the next job terminates.
2004-05-13	* Distributed builds and load balancing now seem to work pretty well.	Eelco Dolstra	1	-24/+74
	(Though the `build-remote.pl' script has a gigantic race condition).
2004-05-13	* Load balancing. `build-remote.pl' will only execute up to a	Eelco Dolstra	1	-1/+1
	per-machine maximum number of parallel jobs on a remote machine.
2004-05-13	* The build hooks used to implement distributed builds can now be run	Eelco Dolstra	2	-134/+352
	in parallel. Hooks are more efficient: locks on output paths are only acquired when the hook says that it is willing to accept a build job. Hooks now work in two phases. First, they should first tell Nix whether they are willing to accept a job. Nix guarantuees that no two hooks will ever be in the first phase at the same time (this simplifies the implementation of hooks, since they don't have to perform locking (?)). Second, if they accept a job, they are then responsible for building it (on the remote system), and copying the result back. These can be run in parallel with other hooks and locally executed jobs. The implementation is a bit messy right now, though. * The directory `distributed' shows a (hacky) example of a hook that distributes build jobs over a set of machines listed in a configuration file.