summary refs log tree commit diff
AgeCommit message (Collapse)Author
2004-06-18* Big refactoring. Move to a much more explicitly state machine basedEelco Dolstra
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
2004-06-18* Shared (garbage collecting) pointers. Copied from Boost.Eelco Dolstra
2004-06-15* Refactoring.Eelco Dolstra
2004-06-08* Cleanup.Eelco Dolstra
2004-06-04* A Nix mode for Emacs.Eelco Dolstra
2004-05-18* Drain the output of the build hook to show error messages. UglyEelco Dolstra
hack.
2004-05-18* Don't set the rpath here --- it's not portable.Eelco Dolstra
2004-05-18* Go back to the old way of generating the system name, and allow itEelco Dolstra
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 onEelco Dolstra
Linux), so use setpgid().
2004-05-14* execl() requires a terminating 0.Eelco Dolstra
* 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
(Though the `build-remote.pl' script has a gigantic race condition).
2004-05-13* Set the executable bit.Eelco Dolstra
2004-05-13* Load balancing. `build-remote.pl' will only execute up to aEelco Dolstra
per-machine maximum number of parallel jobs on a remote machine.
2004-05-13* Perform all tests.Eelco Dolstra
2004-05-13* The build hooks used to implement distributed builds can now be runEelco Dolstra
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
2004-05-12* A switch `-j NUMBER' to set the maximum number of parallel jobs (0 =Eelco Dolstra
no limit). * Add missing file to distribution.
2004-05-12* Broken test.Eelco Dolstra
2004-05-12* Pass to the build hook all sorts of information useful forEelco Dolstra
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
2004-05-11* True parallel builds. Nix can now run as many build jobs inEelco Dolstra
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
* Ignore EINTR in reads and writes.
2004-05-04* A test to verify that Nix executes build jobs in parallel, ifEelco Dolstra
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
* A test to verify that locking of output paths (caused by concurrent invocations of Nix) works correctly.
2004-05-04* Another test.Eelco Dolstra
2004-05-04* Grrr. TESTS are not included in EXTRA_DIST.Eelco Dolstra
2004-05-04* Allow the location of the store etc. to be specified usingEelco Dolstra
environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs.
2004-04-26* Bump the version number.Eelco Dolstra
2004-04-26* Fixed URL.Eelco Dolstra
2004-04-26* Only add `-preRELEASE' to the version if STABLE != 1.Eelco Dolstra
* Documented release procedures.
2004-04-23* Pass SYSTEM through config.h, and allow spaces.Eelco Dolstra
2004-04-22* Look for GC roots in @localstatedir@/nix/gcroots.Eelco Dolstra
2004-04-22* Don't create $(localstatedir)/nix/profiles if --disable-init-stateEelco Dolstra
is specified.
2004-04-21* Dist error.Eelco Dolstra
2004-04-21* Channels. These allow you to stay current with an evolving set ofEelco Dolstra
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
unless `--disable-init-state' is passed to configure.
2004-04-21* Recurse into attribute sets and lists when getting derivations fromEelco Dolstra
an expression.
2004-04-15* Allow extra parameters to be passed to Curl through the `CURL_FLAGS'Eelco Dolstra
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
2004-04-14* `*.gcroot' files can now containing multiple roots.Eelco Dolstra
2004-04-14* Be stricter in verifying store paths.Eelco Dolstra
2004-04-08* Documented the primops.Eelco Dolstra
2004-04-08* EBNF grammar for the Nix expression language.Eelco Dolstra
2004-04-06* Distributed the wrong file.Eelco Dolstra
2004-04-06* Make the creation of user environments much faster and more storageEelco Dolstra
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
2004-04-06* Switched from wget to curl.Eelco Dolstra
* 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
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 derivationEelco Dolstra
binding.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-12-14 04:11:46 +0000