depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2005-03-15	* Some more updates.	Eelco Dolstra	2	-119/+97

2005-03-15	* Remove Docbook EBNF dependency.	Eelco Dolstra	1	-5/+0

2005-03-15	* XInclude all the way.	Eelco Dolstra	8	-52/+43

2005-03-15	* Manual updates.	Eelco Dolstra	4	-71/+13

2005-03-15	* Purify all corepkgs builders.	Eelco Dolstra	5	-15/+17

2005-03-15	* Use SHA-256 for nix-push.	Eelco Dolstra	4	-23/+34

2005-03-14	* Upgrade information.	Eelco Dolstra	1	-0/+21

2005-03-14	* Idem.	Eelco Dolstra	1	-1/+1

2005-03-14	* Pass `--base32' unless using MD5.	Eelco Dolstra	1	-1/+3

2005-03-14	* Bug in clearSubstitutes().	Eelco Dolstra	1	-1/+2

2005-03-14	* Parse new hash format properly.	Eelco Dolstra	1	-6/+15

2005-03-14	* Print SHA-1 hashes in base-32 by default.	Eelco Dolstra	1	-2/+7

2005-03-14	* Prefix hash algorithm in patch generator too.	Eelco Dolstra	1	-8/+9

2005-03-14	* Set NAR name to content hash; previous nix-push names were not	Eelco Dolstra	3	-26/+16
	unique. * Drop `hashAlgo' attribute in manifests; prefix hashes with the hash algorithm instead.
2005-03-14	* Script to garbage collect nix-push directories. It prints out all	Eelco Dolstra	1	-0/+75
	file names in the directory not included in any of the manifests specified on the command line.
2005-03-11	* Preliminary NEWS for 0.8.	Eelco Dolstra	1	-0/+142

2005-03-11	* nix-install-package: install outPath, not drvPath, for now.	Eelco Dolstra	2	-2/+3
	* nix-prefecth-url: print out in base-16.
2005-03-10	* Check for duplicate attributes and formal parameters in Nix	Eelco Dolstra	7	-1/+93
	expressions.
2005-03-07	* In the checker, do traversals of the dependency graph explicitly. A	Eelco Dolstra	2	-45/+152
	conditional expression in the blacklist can specify when to continue/stop a traversal. For example, in <condition> <within> <traverse> <not><hasAttr name='outputHash' value='.+' /></not> </traverse> <hasAttr name='outputHash' value='ef1cb003448b4a53517b8f25adb12452' /> </within> </condition> we traverse the dependency graph, not following the dependencies of `fetchurl' derivations (as indicated by the presence of an `outputHash' attribute - this is a bit ugly). The resulting set of paths is scanned for a fetch of a file with the given hash, in this case, the hash of zlib-1.2.1.tar.gz (which has a security bug). The intent is that a dependency on zlib is not a problem if it is in a `fetchurl' derivation, since that's build-time only. (Other build-time uses of zlib might be a problem, e.g., static linking.)
2005-03-07	* Use XML::LibXML.	Eelco Dolstra	2	-41/+87

2005-03-07	* Automatically add propagated build inputs to user environments.	Eelco Dolstra	1	-1/+15
	Maybe this is a bad idea.
2005-03-04	* Basic blacklist checker. Each element in a user environment is	Eelco Dolstra	2	-3/+122
	checked against every item in a blacklist.
2005-03-03	* Don't use fork() in copyPath(), but a string buffer.	Eelco Dolstra	2	-47/+17

2005-03-03	* Channel fix.	Eelco Dolstra	1	-1/+1

2005-03-03	* Increase Berkeley DB limits a bit more.	Eelco Dolstra	2	-7/+26
	* Maintain the cleanup invariant in clearSubstitutes().
2005-03-02	* Concept for a simple blacklist.	Eelco Dolstra	1	-0/+48

2005-03-02	* `nix-store -q --hash' to quickly query the hash of the contents of a	Eelco Dolstra	3	-6/+28
	store path (which is stored in the database).
2005-03-01	* Doh!	Eelco Dolstra	1	-1/+1

2005-03-01	* Add missing file to dist.	Eelco Dolstra	1	-1/+2

2005-03-01	* Use a weighted use heuristic to disambiguate between multiple	Eelco Dolstra	1	-8/+77
	occurances of a component. If the shortest path distance between a component P and Q in the referers graph is D, then the contribution of Q to the use of P is 1 / R^D, where R >= 1, typically 2. This expresses that distant indirect uses are less important than nearby uses. For instance, this can disambiguate between the bootstrap GCC in Nixpkgs and the GCC of the final stdenv (the former has more uses, but they are further away), and between the GCC of the final stdenv and the GCC+G77 build (the latter has very few uses).
2005-02-28	* Added a disambiguation heuristic: if two components have the same	Eelco Dolstra	2	-4/+24
	name but differ to much in sice (by more than a factor of 3), then never generate a patch.
2005-02-25	* Add a version number to manifests.	Eelco Dolstra	3	-2/+16

2005-02-25	* Pause if errors occur.	Eelco Dolstra	1	-1/+1

2005-02-25	* nix-install-package: Use the new (trivial) package format generated	Eelco Dolstra	1	-21/+34
	by the build farm. See e.g., http://catamaran.labs.cs.uu.nl/dist/nixpkgs-0.8/nixpkgs-0.7pre2302/; the user can click on packages, and they will be installed (assuming the `application/nix-package' MIME type has been associated with `nix-install-package'). Nix expressions are no longer involved: a "package" is just a pointer to a manifest, and the top-level store derivation to be added to the user environment. This makes these packages independent from Nix expression evolution. Note that we install the store derivation ($drvPath), not the resulting output path ($outPath). This is equivalent, except that installing the derivation maintains the back-link from the output path to the derivation that built it. This is useful for maintenance. * Automatically re-exec in an xterm so that the user sees something when `nix-install-package' is run from a browser.
2005-02-24	* Properly specify the hash algorithm in the manifests, and read it	Eelco Dolstra	4	-13/+31
	too. * Change the default hash for nix-prefetch-url back to md5, since that's what we use in Nixpkgs (for now; a birthday attack is rather unlikely there).
2005-02-24	* (Unnecessary) refactoring.	Eelco Dolstra	1	-29/+36

2005-02-23	* When multiple derivations are specified in `nix-store -r', don't	Eelco Dolstra	1	-62/+50
	continue building when one fails unless `--keep-going' is specified. * When `--keep-going' is specified, print out the set of failing derivations at the end (otherwise it can be hard to find out which failed).
2005-02-22	* Support for fixed-output hashes over directory trees (i.e., over the	Eelco Dolstra	3	-16/+35
	NAR dump of the path).
2005-02-22	* Compatibility hack so that Nixpkgs can continue to do hash checking	Eelco Dolstra	2	-1/+10
	in `fetchurl' in Nix <= 0.7, but doesn't in Nix 0.8.
2005-02-18	* Subtle bug in the builder: if a subgoal that is instantiated	Eelco Dolstra	1	-31/+30
	multiple times is also a top-level goal, then the second and later instantiations would never be created because there would be a stable pointer to the first one that would keep it alive in the WeakGoalMap. * Some tracing code for debugging this kind of problem.
2005-02-18	* `make check' fix.	Eelco Dolstra	1	-1/+1

2005-02-17	* `nix-store -q --tree' shows a tree representing the dependency graph	Eelco Dolstra	2	-2/+87
	of the given derivation. Useful for getting a quick overview of how something was built. E.g., to find out how the `baffle' program in your user environment was built, you can do $ nix-store -q --tree $(nix-store -qd $(which baffle)) Tree nesting depth is minimised (?) by topologically sorting paths under the relation A < B iff A \in closure(B).
2005-02-17	* Compatibility hack with older user environments.	Eelco Dolstra	1	-1/+3

2005-02-17	* Switch to the calling user context for some more operations in a	Eelco Dolstra	2	-2/+6
	setuid installation.
2005-02-17	* Put build logs in $prefix/var/nix/log/drvs/.	Eelco Dolstra	2	-1/+2

2005-02-17	* Fix nix-channel.	Eelco Dolstra	2	-25/+63
	* Add `--help' flag; fixes NIX-5. * Add `--remove' flag; fixes NIX-6. * Add `--list' flag.
2005-02-15	* Compatibility with older GCCs.	Eelco Dolstra	1	-5/+15

2005-02-15	* And yet another installation source: the ability to copy user	Eelco Dolstra	1	-34/+46
	environment elements from one user environment to another, e.g., $ nix-env -i --from-profile /nix/var/nix/profiles/other-profile aterm copies the `aterm' component installed in the `other-profile' to the user's current profile.
2005-02-15	* Fix broken GC test.	Eelco Dolstra	2	-1/+9

2005-02-14	* It is now possible to add store derivations or paths directly to a	Eelco Dolstra	4	-10/+52
	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).