depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2004-06-04	* A Nix mode for Emacs.	Eelco Dolstra	6	-2/+118

2004-05-18	* Drain the output of the build hook to show error messages. Ugly	Eelco Dolstra	1	-4/+26
	hack.
2004-05-18	* Don't set the rpath here --- it's not portable.	Eelco Dolstra	1	-2/+2

2004-05-18	* Go back to the old way of generating the system name, and allow it	Eelco Dolstra	1	-3/+6
	to be specified in configure (using `--with-system=SYSTEM').
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	2	-39/+101
	(Though the `build-remote.pl' script has a gigantic race condition).
2004-05-13	* Set the executable bit.	Eelco Dolstra	1	-0/+0

2004-05-13	* Load balancing. `build-remote.pl' will only execute up to a	Eelco Dolstra	4	-11/+34
	per-machine maximum number of parallel jobs on a remote machine.
2004-05-13	* Perform all tests.	Eelco Dolstra	1	-4/+2

2004-05-13	* The build hooks used to implement distributed builds can now be run	Eelco Dolstra	9	-144/+498
	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.
2004-05-12	* Use `-j0'.	Eelco Dolstra	1	-8/+1

2004-05-12	* A switch `-j NUMBER' to set the maximum number of parallel jobs (0 =	Eelco Dolstra	5	-9/+30
	no limit). * Add missing file to distribution.
2004-05-12	* Broken test.	Eelco Dolstra	1	-3/+3

2004-05-12	* Pass to the build hook all sorts of information useful for	Eelco Dolstra	1	-6/+41
	distributing a build action to another machine. In particular, the paths in the input closures, the output paths, and successor mapping for sub-derivations.
2004-05-12	* An quick and dirty hack to support distributed builds.	Eelco Dolstra	9	-13/+92

2004-05-11	* True parallel builds. Nix can now run as many build jobs in	Eelco Dolstra	12	-302/+689
	parallel as possible (similar to GNU Make's `-j' switch). This is useful on SMP systems, but it is especially useful for doing builds on multiple machines. The idea is that a large derivation is initiated on one master machine, which then distributes sub-derivations to any number of slave machines. This should not happen synchronously or in lock-step, so the master must be capable of dealing with multiple parallel build jobs. We now have the infrastructure to support this. TODO: substitutes are currently broken.
2004-05-11	* Ignore interrupt signals while handling an exception.	Eelco Dolstra	1	-4/+15
	* Ignore EINTR in reads and writes.
2004-05-04	* A test to verify that Nix executes build jobs in parallel, if	Eelco Dolstra	5	-3/+81
	possible. This test fails right now because this hasn't been implemented right now. Yes, I'm doing Test-Driven Development! ;-)
2004-05-04	* 1000th revision!	Eelco Dolstra	4	-2/+50
	* A test to verify that locking of output paths (caused by concurrent invocations of Nix) works correctly.
2004-05-04	* Another test.	Eelco Dolstra	6	-2/+66

2004-05-04	* Grrr. TESTS are not included in EXTRA_DIST.	Eelco Dolstra	1	-1/+1

2004-05-04	* Allow the location of the store etc. to be specified using	Eelco Dolstra	9	-13/+86
	environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs.
2004-04-26	* Bump the version number.	Eelco Dolstra	1	-1/+1

2004-04-26	* Fixed URL.	Eelco Dolstra	1	-2/+2

2004-04-26	* Only add `-preRELEASE' to the version if STABLE != 1.	Eelco Dolstra	2	-4/+40
	* Documented release procedures.
2004-04-23	* Pass SYSTEM through config.h, and allow spaces.	Eelco Dolstra	3	-2/+6

2004-04-22	* Look for GC roots in @localstatedir@/nix/gcroots.	Eelco Dolstra	2	-20/+58

2004-04-22	* Don't create $(localstatedir)/nix/profiles if --disable-init-state	Eelco Dolstra	2	-3/+1
	is specified.
2004-04-21	* Dist error.	Eelco Dolstra	1	-1/+1

2004-04-21	* Channels. These allow you to stay current with an evolving set of	Eelco Dolstra	10	-52/+194
	Nix expressions. To subscribe to a channel (needs to be done only once): nix-channel --add \ http://catamaran.labs.cs.uu.nl/dist/nix/channels/nixpkgs-unstable This just adds the given URL to ~/.nix-channels (which can also be edited manually). To update from all channels: nix-channel --update This fetches the latest expressions and pulls cache manifests. The default Nix expression (~/.nix-defexpr) is made to point to the conjunction of the expressions downloaded from all channels. So to update all installed derivations in the current user environment: nix-channel --update nix-env --upgrade '*' If you are really courageous, you can put this in a cronjob or something. You can subscribe to multiple channels. It is not entirely clear what happens when there are name clashes between derivations from different channels. From nix-env/main.cc it appears that the one with the lowest (highest?) hash will be used, which is pretty meaningless.
2004-04-21	* Do initialise state (the DB etc.) when doing a `make install',	Eelco Dolstra	4	-8/+18
	unless `--disable-init-state' is passed to configure.
2004-04-21	* Recurse into attribute sets and lists when getting derivations from	Eelco Dolstra	1	-0/+4
	an expression.
2004-04-15	* Allow extra parameters to be passed to Curl through the `CURL_FLAGS'	Eelco Dolstra	1	-1/+1
	environment variable. This is useful for passing authentication information (it won't show up in `ps'). Hacky - nix-push should abstract over the use of Curl.
2004-04-14	* Use @storedir@, not @prefix@/store.	Eelco Dolstra	1	-1/+1

2004-04-14	* `*.gcroot' files can now containing multiple roots.	Eelco Dolstra	1	-3/+7

2004-04-14	* Be stricter in verifying store paths.	Eelco Dolstra	3	-4/+9

2004-04-08	* Documented the primops.	Eelco Dolstra	2	-3/+102

2004-04-08	* EBNF grammar for the Nix expression language.	Eelco Dolstra	4	-4/+198

2004-04-06	* Distributed the wrong file.	Eelco Dolstra	1	-2/+1

2004-04-06	* Make the creation of user environments much faster and more storage	Eelco Dolstra	1	-45/+66
	efficient by creating only a single symlink to entire directory trees unless a collission occurs.
2004-04-06	* Fail if prerequisites are missing.	Eelco Dolstra	1	-11/+14

2004-04-06	* Switched from wget to curl.	Eelco Dolstra	11	-36/+47
	* Made the dependencies on bzip2 and the shell explicit.
2004-04-05	* When something goes wrong in the evaluation of a Nix expression,	Eelco Dolstra	8	-89/+200
	print a nice backtrace of the stack, rather than vomiting a gigantic (and useless) aterm on the screen. Example: error: while evaluating file `.../pkgs/system/test.nix': while evaluating attribute `subversion' at `.../pkgs/system/all-packages-generic.nix', line 533: while evaluating function at `.../pkgs/applications/version-management/subversion/default.nix', line 1: assertion failed at `.../pkgs/applications/version-management/subversion/default.nix', line 13 Since the Nix expression language is lazy, the trace may be misleading. The purpose is to provide a hint as to the location of the problem.
2004-04-02	* Print a more useful error message in case of an invalid derivation	Eelco Dolstra	1	-1/+6
	binding.
2004-03-30	* The recent change in nixpkgs of calling `stdenv.mkDerivation'	Eelco Dolstra	2	-2/+11
	instead of `derivation' triggered a huge slowdown in the Nix expression evaluator. Total execution time of `nix-env -qa' went up by a factor of 60 or so. This scalability problem was caused by expressions such as (x: y: ... x ...) a b where `a' is a large term (say, the one in `all-packages-generic.nix'). Then the first beta-reduction would produce (y: ... a ...) b by substituting `a' for `x'. The second beta-reduction would then substitute `b' for `y' into the body `... a ...', which is a large term due to `a', and thus causes a large traversal to be performed by substitute() in the second reduction. This is however entirely redundant, since `a' cannot contain free variables (since we never substitute below a weak head normal form). The solution is to wrap substituted terms into a `Closed' constructor, i.e., subst(subs, Var(x)) = Closed(e) iff subs[x] = e have substitution not descent into closed terms, subst(subs, Closed(x)) = Closed(x) and otherwise ignore them for evaluation, eval(Closed(x)) = eval(x). * Fix a typo that caused incorrect substitutions to be performed in simple lambdas, e.g., `(x: x: x) a' would reduce to `(x: a)'.
2004-03-29	* Specify Perl as a dependency for the RPM.	Eelco Dolstra	1	-0/+1

2004-03-28	* Added an operator `?' to test for attribute existence, e.g.,	Eelco Dolstra	2	-1/+10
	`attrs ? x' yields true iff `attrs' has an attribute named `x'.
2004-03-28	* Added an operator `~' to select paths within a derivation. E.g.,	Eelco Dolstra	3	-0/+16
	{stdenv, bash}: derivation { builder = bash ~ /bin/sh; args = ["-e" "-x" ./builder.sh]; ... } Here the attribute `builder' will evaluate to, e.g., `/nix/store/1234abcd...-bash-2.0.1/bin/sh'.
2004-03-28	* Added plain lambdas, e.g., `let { id = x: x; const = x: y: x; }'.	Eelco Dolstra	5	-37/+63
	`bla:' is now no longer parsed as a URL. * Re-enabled support for the `args' attribute in derivations to specify command line arguments to the builder, e.g., ... builder = /usr/bin/python; args = ["-c" ./builder.py]; ...