about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2004-06-29 * Write build logs to disk again.Eelco Dolstra1-1/+29
2004-06-28 * By default, `nix-env -i' now deletes previously installedEelco Dolstra1-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 correspondingEelco Dolstra1-0/+6
normalisation goal.
2004-06-28 * `nix-env -u' now allows a specific version to be specified whenEelco Dolstra1-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 Dolstra11-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, asEelco Dolstra5-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 theEelco Dolstra1-58/+214
goal and allow the problem to be handled elsewhere (e.g., at top-level).
2004-06-24 * Obsolete.Eelco Dolstra1-162/+0
2004-06-24 * Multiple and/or failing substitutes now work.Eelco Dolstra1-12/+42
2004-06-22 * ArghhhhhhEelco Dolstra1-1/+1
2004-06-22 * Some more diagnostics changes.Eelco Dolstra2-25/+41
2004-06-22 * Well, it's better than printf.Eelco Dolstra1-1/+1
2004-06-22 * Started making Nix's diagnostic messages a bit more useful.Eelco Dolstra1-10/+26
2004-06-22 * Put WEXITSTATUS stuff somewhere else.Eelco Dolstra4-3/+11
2004-06-22 * Reduce gratuitous cut & pasting.Eelco Dolstra1-68/+55
2004-06-22 * Wrapper class around pids.Eelco Dolstra4-87/+162
2004-06-22 * Substitutes should occupy a build slot.Eelco Dolstra1-1/+15
2004-06-22 * Refactoring.Eelco Dolstra4-20/+25
2004-06-21 * Remove debug output.Eelco Dolstra1-1/+0
2004-06-21 * Acquire a lock on the output path when running a substitute. AlsoEelco Dolstra1-0/+22
delete obstructing invalid paths.
2004-06-21 * Ugh, nasty Heisenbug due to an uninitialiased variable. The bugEelco Dolstra1-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 Dolstra1-0/+6
2004-06-21 * Wrap calls to registerSubstitute() in a single transaction toEelco Dolstra3-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_NOSYNCEelco Dolstra1-0/+8
flag doesn't seem to work as advertised.
2004-06-20 * Re-enable support for substitutes in the normaliser.Eelco Dolstra5-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 Dolstra3-41/+52
2004-06-19 * Re-enable build hooks.Eelco Dolstra1-72/+325
2004-06-18 * Big refactoring. Move to a much more explicitly state machine basedEelco Dolstra3-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 Dolstra3-1/+263
2004-06-18 * Shared (garbage collecting) pointers. Copied from Boost.Eelco Dolstra12-17/+1268
2004-06-15 * Refactoring.Eelco Dolstra3-83/+57
2004-06-08 * Cleanup.Eelco Dolstra1-10/+17
2004-05-18 * Drain the output of the build hook to show error messages. UglyEelco Dolstra1-4/+26
hack.
2004-05-18 * setpgrp() is not POSIX (and on Mac OS X it's different than onEelco Dolstra1-1/+1
Linux), so use setpgid().
2004-05-14 * execl() requires a terminating 0.Eelco Dolstra1-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 Dolstra1-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 aEelco Dolstra1-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 runEelco Dolstra2-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.
2004-05-12 * A switch `-j NUMBER' to set the maximum number of parallel jobs (0 =Eelco Dolstra4-8/+29
no limit). * Add missing file to distribution.
2004-05-12 * Pass to the build hook all sorts of information useful forEelco Dolstra1-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 Dolstra5-11/+33
2004-05-11 * True parallel builds. Nix can now run as many build jobs inEelco Dolstra8-288/+676
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 Dolstra1-4/+15
* Ignore EINTR in reads and writes.
2004-05-04 * Allow the location of the store etc. to be specified usingEelco Dolstra1-12/+19
environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs.
2004-04-23 * Pass SYSTEM through config.h, and allow spaces.Eelco Dolstra2-1/+3
2004-04-22 * Don't create $(localstatedir)/nix/profiles if --disable-init-stateEelco Dolstra1-3/+0
is specified.
2004-04-21 * Do initialise state (the DB etc.) when doing a `make install',Eelco Dolstra1-7/+0
unless `--disable-init-state' is passed to configure.
2004-04-21 * Recurse into attribute sets and lists when getting derivations fromEelco Dolstra1-0/+4
an expression.
2004-04-14 * Be stricter in verifying store paths.Eelco Dolstra3-4/+9
2004-04-05 * When something goes wrong in the evaluation of a Nix expression,Eelco Dolstra8-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.