depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2005-01-27	* Make lock removal safe by signalling to blocked processes that the	Eelco Dolstra	2	-24/+45
	lock they are waiting on has become stale (we do this by writing a meaningless token to the unlinked file).
2005-01-25	* Maintain the references/referers relation also for derivations.	Eelco Dolstra	6	-80/+46
	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	* Simplification: registerSubstitutes -> registerSubstitute. We no	Eelco Dolstra	3	-20/+11
	longer need the former since there we no longer have the substitutes-rev table (which triggered a O(n^2) cost in updating them).
2005-01-25	* Really fix the substitute mechanism, i.e., ensure the closure	Eelco Dolstra	2	-11/+36
	invariant by registering references through the manifest. * Added a test for nix-pull.
2005-01-25	* Fix the `--fallback' switch.	Eelco Dolstra	1	-0/+6
	* Fix the substitutes tests.
2005-01-25	* Fix the build hook mechanism; pass the pointer graph to the hook.	Eelco Dolstra	1	-2/+24

2005-01-25	* In nix-store: added query `--referers-closure' that returns the	Eelco Dolstra	2	-5/+11
	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-25	* In nix-store: change `--build' back to `--realise'. Also brought	Eelco Dolstra	1	-37/+57
	back the query flag `--force-realise'. * Fixed some of the tests.
2005-01-20	* Terminology fixes.	Eelco Dolstra	5	-22/+22

2005-01-20	* Another change to low-level derivations. The last one this year, I	Eelco Dolstra	5	-25/+59
	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	* Nix-store queries `--references' and `referers' to query the pointer	Eelco Dolstra	2	-0/+14
	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	11	-88/+118
	`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	2	-22/+32
	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	6	-94/+71
	* Re-enable `nix-store --query --requisites'.
2005-01-19	* Started removing closure store expressions, i.e., the explicit	Eelco Dolstra	9	-750/+327
	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	* 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	7	-33/+103
	* 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	2	-9/+11
	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	4	-24/+41
	* 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-13	* Added SHA-1 support. `nix-hash' now has an option `--type sha1' to	Eelco Dolstra	2	-2/+2
	select SHA-1 hashing.
2005-01-13	* Refactoring to support SHA-1.	Eelco Dolstra	1	-1/+1

2005-01-04	* Cygwin compatibility.	Eelco Dolstra	1	-0/+1

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	3	-121/+28
	- 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-11-29	* utime() follows symlinks, so don't change the mtime if the file is a	Eelco Dolstra	1	-7/+8
	symlink.
2004-11-29	* Remove debug statement.	Eelco Dolstra	1	-2/+0

2004-11-29	* Canonicalise metadata of all files in store paths (set the mtime to	Eelco Dolstra	1	-2/+58
	0, set the mode to either 444 or 555, set the group to the default).
2004-11-03	* string2ATerm -> overloaded toATerm.	Eelco Dolstra	1	-7/+7

2004-10-29	* Drop ATmake / ATMatcher also in handling store expressions.	Eelco Dolstra	3	-31/+46

2004-10-25	* Allow certain operations to succeed even if we don't have write	Eelco Dolstra	6	-10/+42
	permission to the Nix store or database. E.g., `nix-env -qa' will work, but `nix-env -qas' won't (the latter needs DB access). The option `--readonly-mode' forces this mode; otherwise, it's only activated when the database cannot be opened.
2004-09-22	* Make store objects created by substitutes read-only.	Eelco Dolstra	1	-0/+2

2004-09-12	* Fallback didn't work for subderivations of an unnormalised the main	Eelco Dolstra	1	-44/+7
	derivation, since NormalisationGoal would first run a NormalisationGoal on the subderivation (a no-op, since in a situation where we need fallback the successor is known), and then runs a RealisationGoal on the normal form, which then cannot do a fallback because it doesn't know the derivation expression for which it is a normal form. Tossed out the 2-phase normalisation/realisation in NormalisationGoal and SubstitutionGoal since it's no longer needed - a RealisationGoal will run a NormalisationGoal if necessary.
2004-09-09	* Remove write permission from store objects after they have been	Eelco Dolstra	1	-0/+4
	added to the store. Bug reported by Martin.
2004-09-09	* A very dirty hack to make setuid installations a bit nicer to use.	Eelco Dolstra	1	-2/+9
	Previously there was the problem that all files read by nix-env etc. should be reachable and readable by the Nix user. So for instance building a Nix expression in your home directory meant that the home directory should have at least g+x or o+x permission so that the Nix user could reach the Nix expression. Now we just switch back to the original user just prior to reading sources and the like. The places where this happens are somewhat arbitrary, however. Any scope that has a live SwitchToOriginalUser object in it is executed as the original user. * Back out r1385. setreuid() sets the saved uid to the new real/effective uid, which prevents us from switching back to the original uid. setresuid() doesn't have this problem (although the manpage has a bug: specifying -1 for the saved uid doesn't leave it unchanged; an explicit value must be specified).
2004-08-31	* Main the `substitutes-rev' table again, but now in a way that	Eelco Dolstra	2	-20/+36
	doesn't take \Theta(n^2) space/time complexity.
2004-08-31	* Quadruple the Berkeley DB locking limits to get rid of out of memory	Eelco Dolstra	1	-2/+21
	errors while running `nix-store --verify'.
2004-08-30	* Removed nrWaitees field. It was redundant with waitees.size() and	Eelco Dolstra	1	-24/+5
	could get out of sync if multiple input derivations mapped to the same closure expression (since waitees is a set).
2004-08-25	* `--min-age' flag in nix-store and nix-collect-garbage to only delete	Eelco Dolstra	2	-3/+20
	unreachable paths that haven't been used for N hours. For instance, `nix-collect-garbage --min-age 168' only deletes paths that haven't been accessed in the last week. This is useful for instance in the build farm where many derivations can be shared between consecutive builds, and we wouldn't want a garbage collect to throw them all away. We could of course register them as roots, but then we'd to unregister them at some point, which would be a pain to manage. The `--min-age' flag gives us a sort of MRU caching scheme. BUG: this really shouldn't be in gc.cc since that violates mechanism/policy separation.
2004-08-25	* Put the garbage collector in nix-store: operation `--gc',	Eelco Dolstra	5	-6/+110
	suboperations `--print-live', `--print-dead', and `--delete'. The roots are not determined by nix-store; they are read from standard input. This is to make it easy to customise what the roots are. The collector now no longer fails when store expressions are missing (which legally happens when using substitutes). It never tries to fetch paths through substitutes. TODO: acquire a global lock on the store while garbage collecting. * Removed `nix-store --delete'.
2004-08-18	* The default verbosity level of all Nix commands is now lvlInfo.	Eelco Dolstra	1	-1/+1
	* Builder output is written to standard error by default. * The option `-B' is gone. * The option `-Q' suppresses builder output. The result of this is that most Nix invocations shouldn't need any flags w.r.t. logging.
2004-08-11	* The predecessor of a successor need not be present. This in	Eelco Dolstra	1	-4/+6
	particular happens on distributed builds or when using push/pull.
2004-08-05	* Clean up the temporary directory for hook communication (and don't	Eelco Dolstra	1	-0/+1
	print out incorrect "build failed" messages).
2004-08-04	* Creating a file nix-support/no-scan in the output path of a	Eelco Dolstra	1	-2/+5
	derivation disables scanning for dependencies. Use at your own risk. This is a quick hack to speed up UML image generation (image are very big, say 1 GB). It would be better if the scanner were faster, and didn't read the whole file into memory.
2004-07-06	* Fixed format string error.	Eelco Dolstra	1	-1/+1

2004-07-01	* Don't go into a (sometimes infinite) loop calling the build hook.	Eelco Dolstra	1	-16/+24

2004-07-01	* Include some missing headers.	Eelco Dolstra	1	-0/+1

2004-06-29	* Write build logs to disk again.	Eelco Dolstra	1	-1/+29

2004-06-28	* In a realisation goal, check the result of the corresponding	Eelco Dolstra	1	-0/+6
	normalisation goal.
2004-06-28	* Added a switch `--fallback'. From the manual:	Eelco Dolstra	8	-48/+149
	Whenever Nix attempts to realise a derivation for which a closure is already known, but this closure cannot be realised, fall back on normalising the derivation. The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository. If the repository is down, the realisation of the derivation will fail. When this option is specified, Nix will build the derivation instead. Thus, binary installation falls back on a source installation. This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
2004-06-25	* A flag `--keep-going / -k' to keep building goals if one fails, as	Eelco Dolstra	3	-130/+157
	much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags.