depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2005-01-20	* Another change to low-level derivations. The last one this year, I	Eelco Dolstra	7	-32/+70
	promise :-) This allows derivations to specify on what output paths of input derivations they are dependent. This helps to prevent unnecessary downloads. For instance, a build might be dependent on the `devel' and `lib' outputs of some library component, but not the `docs' output.
2005-01-19	* Set the Perl search path properly (reported by Roy van den Broek).	Eelco Dolstra	1	-1/+1

2005-01-19	* Nix-store queries `--references' and `referers' to query the pointer	Eelco Dolstra	3	-18/+33
	graph. That is, `nix-store --query --references PATH' shows the set of paths referenced by PATH, and `nix-store --query --referers PATH' shows the set of paths referencing PATH.
2005-01-19	* Renamed `normalise.cc' -> `build.cc', `storeexprs.cc' ->	Eelco Dolstra	19	-98/+128
	`derivations.cc', etc. * Store the SHA-256 content hash of store paths in the database after they have been built/added. This is so that we can check whether the store has been messed with (a la `rpm --verify'). * When registering path validity, verify that the closure property holds.
2005-01-19	* `nix-store --build' now builds its arguments in parallel instead of	Eelco Dolstra	4	-24/+37
	sequentially (within the limits set by `--jobs'). This should greatly improve the utilisation of the build farm when doing Nixpkgs builds.
2005-01-19	* Change extension `.store' to `.drv'.	Eelco Dolstra	12	-139/+120
	* Re-enable `nix-store --query --requisites'.
2005-01-19	* Started removing closure store expressions, i.e., the explicit	Eelco Dolstra	15	-891/+408
	representation of closures as ATerms in the Nix store. Instead, the file system pointer graph is now stored in the Nix database. This has many advantages: - It greatly simplifies the implementation (we can drop the notion of `successors', and so on). - It makes registering roots for the garbage collector much easier. Instead of specifying the closure expression as a root, you can simply specify the store path that must be retained as a root. This could not be done previously, since there was no way to find the closure store expression containing a given store path. - Better traceability: it is now possible to query what paths are referenced by a path, and what paths refer to a path.
2005-01-19	* Support arities > 6.	Eelco Dolstra	1	-1/+7

2005-01-18	* Get --readonly-mode to work again.	Eelco Dolstra	1	-0/+11

2005-01-17	* Actually check that the result of fixed-output derivations matches	Eelco Dolstra	1	-0/+25
	the specified hash.
2005-01-17	* Removed the `id' attribute hack.	Eelco Dolstra	17	-101/+292
	* Formalise the notion of fixed-output derivations, i.e., derivations for which a cryptographic hash of the output is known in advance. Changes to such derivations should not propagate upwards through the dependency graph. Previously this was done by specifying the hash component of the output path through the `id' attribute, but this is insecure since you can lie about it (i.e., you can specify any hash and then produce a completely different output). Now the responsibility for checking the output is moved from the builder to Nix itself. A fixed-output derivation can be created by specifying the `outputHash' and `outputHashAlgo' attributes, the latter taking values `md5', `sha1', and `sha256', and the former specifying the actual hash in hexadecimal or in base-32 (auto-detected by looking at the length of the attribute value). MD5 is included for compatibility but should be considered deprecated. * Removed the `drvPath' pseudo-attribute in derivation results. It's no longer necessary. * Cleaned up the support for multiple output paths in derivation store expressions. Each output now has a unique identifier (e.g., `out', `devel', `docs'). Previously there was no way to tell output paths apart at the store expression level. * `nix-hash' now has a flag `--base32' to specify that the hash should be printed in base-32 notation. * `fetchurl' accepts parameters `sha256' and `sha1' in addition to `md5'. * `nix-prefetch-url' now prints out a SHA-1 hash in base-32. (TODO: a flag to specify the hash.)
2005-01-14	* Shorten SHA-256 hashes used in store path name generation to 160	Eelco Dolstra	7	-36/+108
	bits, then encode them in a radix-32 representation (using digits and letters except e, o, u, and t). This produces store paths like /nix/store/4i0zb0z7f88mwghjirkz702a71dcfivn-aterm-2.3.1. The nice thing about this is that the hash part of the file name is still 32 characters, as before with MD5. (Of course, shortening SHA-256 to 160 bits makes it no better than SHA-160 in theory, but hopefully it's a bit more resistant to attacks; it's certainly a lot slower.)
2005-01-14	* Start move towards SHA-256 hashes instead of MD5.	Eelco Dolstra	9	-34/+63
	* Start cleaning up unique store path generation (they weren't always unique; in particular the suffix ("-aterm-2.2", "-builder.sh") was not part of the hash, therefore changes to the suffix would cause multiple store objects with the same hash).
2005-01-14	* Missing file.	Eelco Dolstra	1	-0/+50

2005-01-14	* Use absolute paths.	Eelco Dolstra	2	-8/+8

2005-01-14	* Add SHA-256.	Eelco Dolstra	9	-8/+912
	* Tests for the various hashes.
2005-01-14	* Removed some dead code.	Eelco Dolstra	2	-152/+1

2005-01-13	* Added SHA-1 support. `nix-hash' now has an option `--type sha1' to	Eelco Dolstra	9	-26/+487
	select SHA-1 hashing.
2005-01-13	* Refactoring to support SHA-1.	Eelco Dolstra	6	-18/+36

2005-01-12	* Bump version number to 0.8.	Eelco Dolstra	1	-1/+1

2005-01-12	* Script to remove patches from manifests.	Eelco Dolstra	1	-0/+19

2005-01-12	* Print out less garbage.	Eelco Dolstra	1	-8/+10

2005-01-12	* NEWS and manual update for release 0.7.	Eelco Dolstra	3	-1/+41

2005-01-05	* Prototype store optimiser. It searched the Nix store for identical	Eelco Dolstra	1	-0/+69
	files and hard-links them to each other to save disk space. Currently it doesn't actually do the hard-linking, it just reports the amount of space saved if it did.
2005-01-04	* Cygwin compatibility.	Eelco Dolstra	2	-2/+3

2004-12-31	* Remove old stuff.	Eelco Dolstra	1	-59/+0

2004-12-31	* If a patch already exists, it must still be included in the manifest.	Eelco Dolstra	1	-7/+10

2004-12-30	* More instrumentation (statistics go to /nix/var/log/nix/downloads).	Eelco Dolstra	1	-1/+6

2004-12-30	* Fix handling of chained patches: don't skip patches if intermediate	Eelco Dolstra	1	-13/+20
	paths are missing, etc.
2004-12-30	* Some logging for evaluation.	Eelco Dolstra	2	-0/+16

2004-12-29	* Propagate patches from the source distribution to the destination	Eelco Dolstra	3	-18/+68
	distribution insofar they are applicable.
2004-12-29	* Integrated bsdiff/bspatch 4.2 (from	Eelco Dolstra	9	-1/+817
	http://www.daemonology.net/bsdiff/bsdiff-4.2.tar.gz) into the source tree. The license is a bit peculiar, but it does allow verbatim copying, which is what we do here (i.e., so don't make any changes to the sources).
2004-12-29	* Reject patches larger than the full archives they produce.	Eelco Dolstra	1	-6/+12

2004-12-29	* Atomic file replacement is good.	Eelco Dolstra	2	-3/+14

2004-12-29	* A utility to generate patches between releases based on their	Eelco Dolstra	2	-25/+249
	manifests.
2004-12-29	* Use aterm 2.3.1.	Eelco Dolstra	1	-3/+3

2004-12-28	* A small utility to add the Size and NarHash fields to old manifests.	Eelco Dolstra	1	-0/+53

2004-12-28	* Added a function to write manifests.	Eelco Dolstra	2	-41/+86

2004-12-20	* Place manifests in /nix/var/nix/manifests.	Eelco Dolstra	12	-79/+35
	* Use the new patch downloader.
2004-12-20	* Sync with changed substitute mechanism.	Eelco Dolstra	3	-6/+11
	* Accept the NarHash line. * Clear substitutes in `nix-channel --update'.
2004-12-20	* I love test sets.	Eelco Dolstra	3	-18/+21

2004-12-20	* An operation `nix-store --clear-substitutes' to remove all	Eelco Dolstra	1	-8/+35
	registered substitute mappings.
2004-12-20	* Simplify the substitute mechanism:	Eelco Dolstra	5	-122/+42
	- Drop the store expression. So now a substitute is just a command-line invocation (a program name + arguments). If you register a substitute you are responsible for registering the expression that built it (if any) as a root of the garbage collector. - Drop the substitutes-rev DB table.
2004-12-17	* Typo: genericBuilder -> genericBuild.	Eelco Dolstra	1	-2/+2

2004-12-16	* Fix nix-pull.	Eelco Dolstra	1	-11/+14

2004-12-16	* Commit old changed to bdiff.sh - but bdiff.sh is obsolete.	Eelco Dolstra	1	-14/+26

2004-12-16	* Remove `prebuilts.conf' file, it's not like anybody was using it.	Eelco Dolstra	3	-19/+5
	* Add /nix/var/nix/manifests directory.
2004-12-13	* Include the size of the bzipped archive (necessary for computing the	Eelco Dolstra	2	-9/+23
	cheapest download path), as well as the hash of the contents of the path (necessary for checking patch applicability).
2004-12-13	* Patch deployment. `download.pl' (intended to be used in the	Eelco Dolstra	3	-34/+323
	substitute mechanism) creates a store path by downloading full NAR archives and/or patches specified in the available manifests. Any combination of present paths, full downloads, and patches can be used to construct the target path. In particular, patches can be chained in sequence; and full NAR archives of the target path can be omitted (i.e., patch-only deployment is possible). A shortest path algorithm is used to find the smallest set of files to be downloaded (the edge weights are currently file sizes, but one can imagine taking the network speed to the various source into account). Patches are binary deltas between two store paths. To be precise, they are the output of the `bsdiff' program applied to the NAR archives obtained by dumping (`nix-store --dump') the two store paths. The advantage of diff'ing NAR archives (and not, say, doing file-by-file diffs) is that file renames/moves are handled automatically. The disadvantage is that we cannot optimise creation of unchanged files (by hard-linking).
2004-12-13	* Allow an optional hash to be provided. This prevents redundant	Eelco Dolstra	1	-20/+26
	fetches.