depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2006-11-30	* More remote operations.	Eelco Dolstra	1	-2/+2
	* Added new operation hasSubstitutes(), which is more efficient than querySubstitutes().size() > 0.
2006-11-30	* Put building in the store API.	Eelco Dolstra	1	-2/+1

2006-11-30	* Refactoring. There is now an abstract interface class StoreAPI	Eelco Dolstra	1	-9/+9
	containing functions that operate on the Nix store. One implementation is LocalStore, which operates on the Nix store directly. The next step, to enable secure multi-user Nix, is to create a different implementation RemoteStore that talks to a privileged daemon process that uses LocalStore to perform the actual operations.
2006-09-04	* Remove unnecessary inclusions of aterm2.h.	Eelco Dolstra	1	-0/+2

2006-09-04	* Use a proper namespace.	Eelco Dolstra	1	-0/+9
	* Optimise header file usage a bit. * Compile the parser as C++.
2006-03-06	* `nix-env (-i\|-u) --dry-run' now shows exactly which missing paths	Eelco Dolstra	1	-1/+46
	will be built or substituted.
2005-12-13	* Change `referer' to `referrer' throughout. In particular, the	Eelco Dolstra	1	-1/+1
	nix-store query options `--referer' and `--referer-closure' have been changed to `--referrer' and `--referrer-closure' (but the old ones are still accepted for compatibility).
2005-02-14	* It is now possible to add store derivations or paths directly to a	Eelco Dolstra	1	-0/+9
	user environment, e.g., $ nix-env -i /nix/store/z58v41v21xd3ywrqk1vmvdwlagjx7f10-aterm-2.3.1.drv or $ nix-env -i /nix/store/hsyj5pbn0d9iz7q0aj0fga7cpaadvp1l-aterm-2.3.1 This is useful because it allows Nix expressions to be bypassed entirely. For instance, if only a nix-pull manifest is provided, plus the top-level path of some component, it can be installed without having to supply the Nix expression (e.g., for obfuscation, or to be independent of Nix expression language changes or context dependencies).
2005-02-08	* Updated `nix-store --verify' to the new schema.	Eelco Dolstra	1	-2/+2

2005-01-25	* Maintain the references/referers relation also for derivations.	Eelco Dolstra	1	-41/+0
	This simplifies garbage collection and `nix-store --query --requisites' since we no longer need to treat derivations specially. * Better maintaining of the invariants, e.g., setReferences() can only be called on a valid/substitutable path.
2005-01-25	* In nix-store: added query `--referers-closure' that returns the	Eelco Dolstra	1	-3/+6
	closure of the referers relation rather than the references relation, i.e., the set of all paths that directly or indirectly refer to the given path. Note that contrary to the references closure this set is not fixed; it can change as paths are added to or removed from the store.
2005-01-20	* Another change to low-level derivations. The last one this year, I	Eelco Dolstra	1	-2/+5
	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	* Renamed `normalise.cc' -> `build.cc', `storeexprs.cc' ->	Eelco Dolstra	1	-1/+1
	`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	* Change extension `.store' to `.drv'.	Eelco Dolstra	1	-51/+25
	* Re-enable `nix-store --query --requisites'.
2005-01-19	* Started removing closure store expressions, i.e., the explicit	Eelco Dolstra	1	-6/+23
	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-17	* Removed the `id' attribute hack.	Eelco Dolstra	1	-2/+3
	* 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.)
2004-06-18	* Big refactoring. Move to a much more explicitly state machine based	Eelco Dolstra	1	-0/+72
	approach. This makes it much easier to add extra complexity in the normaliser / realiser (e.g., build hooks, substitutes).