4 commits

Author	SHA1	Message	Date
Eelco Dolstra	54664b6fb7	* The write() system call can write less than the requested ... number of bytes, e.g., in case of a signal like SIGSTOP. This caused `nix --dump' to fail sometimes. Note that this bug went unnoticed because the call to `nix --dump' is in a pipeline, and the shell ignores non-zero exit codes from all but the last element in the pipeline. Is there any way to check the result of the initial elements in the pipeline? (In other words, is it at all possible to write reliable shell scripts?)	2003-07-16 21:24:02 +00:00
Eelco Dolstra	9d56ca219f	* Substitute fixes.	2003-07-16 20:00:51 +00:00
Eelco Dolstra	822c072cfa	* Compress Nix archives when pushing them.	2003-07-10 20:34:29 +00:00
Eelco Dolstra	d072485d28	* Get `nix-push' working again. It now uses Nix/Fix to create Nix ... archives (using the package in corepkgs/nar). * queryPathByHash -> expandHash, and it takes an argument specifying the target path (which may be empty). * Install the core Fix packages in $prefix/share/fix. TODO: bootstrap Nix and install Nix as a Fix package.	2003-07-10 13:41:28 +00:00