about summary refs log tree commit diff
path: root/corepkgs
AgeCommit message (Collapse)AuthorFilesLines
2003-07-30 * INSTALL_DATA -> INSTALL_PROGRAM to ensure that the execute bitEelco Dolstra2-3/+3
remains set.
2003-07-23 * Incorporated Berkeley DB and ATerm into the source tree.Eelco Dolstra2-0/+4
* `make dist'.
2003-07-22 * Substitutes now should produce a path with the same id as they areEelco Dolstra1-0/+1
substituting for (obvious, really). * For greater efficiency, nix-pull/unnar will place the output in a path that is probably the same as what is actually needed, thus preventing a path copy. * Even if a output id is given in a Fix package expression, ensure that the resulting Nix derive expression has a different id. This is because Nix expressions that are semantically equivalent (i.e., build the same result) might be different w.r.t. efficiency or divergence. It is absolutely vital for the substitute mechanism that such expressions are not used interchangeably.
2003-07-21 * Syntax fixes.Eelco Dolstra2-3/+8
* When pushing, put the hash in the file name so that the client can verify (proof-carrying file names?).
2003-07-21 * Allow the output/expression id to be forced to a certain Eelco Dolstra2-5/+4
value; this potentially dangerous feature enables better sharing for those paths for which the content is known in advance (e.g., because a content hash is given). * Fast builds: if we can expand all output paths of a derive expression, we don't have to build.
2003-07-18 * Generate nar.sh, fetchurl.sh.Eelco Dolstra7-19/+28
2003-07-16 * The write() system call can write less than the requested Eelco Dolstra1-0/+2
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 * Doh!Eelco Dolstra1-1/+2
2003-07-16 * Substitute fixes.Eelco Dolstra2-4/+6
2003-07-12 * Fetchurl: check md5 checksum.Eelco Dolstra2-3/+10
2003-07-10 * Compress Nix archives when pushing them.Eelco Dolstra2-2/+2
2003-07-10 * The policy-free derivate sharing now *almost* works. :-) For anyEelco Dolstra3-0/+13
hash for which no local expansion is available, Nix can execute a `substitute' which should produce a path with such a hash. This is policy-free since Nix does not in any way specify how the substitute should work, i.e., it's an arbitrary (unnormalised) fstate expression. For example, `nix-pull' registers substitutes that fetch Nix archives from the network (through `wget') and unpack them, but any other method is possible as well. This is an improvement over the old Nix sharing scheme, which had a policy (fetching through `wget') built in. The sharing scheme doesn't work completely yet because successors from fstate rewriting have to be registered on the receiving side. Probably the whole successor stuff can be folded up into the substitute mechanism; this would be a nice simplification.
2003-07-10 * Get `nix-push' working again. It now uses Nix/Fix to create NixEelco Dolstra3-0/+19
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 * Moved the fetchutl package to corepkgs.Eelco Dolstra2-0/+12