about summary refs log tree commit diff
path: root/src/fstate.hh
AgeCommit message (Collapse)AuthorFilesLines
2003-07-17 * For debugging: `nix --verify' to check the consistency of theEelco Dolstra1-4/+0
database and store.
2003-07-16 * Fix the -qr query.Eelco Dolstra1-1/+6
2003-07-16 * Fix self-referential outputs.Eelco Dolstra1-15/+1
* Fix -qp query.
2003-07-15 * Get Fix and Nix to work again.Eelco Dolstra1-0/+2
2003-07-15 * The new normaliser now passes the unit tests.Eelco Dolstra1-1/+1
2003-07-15 * Basic work on allowing derive expressions to build multiple paths.Eelco Dolstra1-19/+38
This is not entirely trivial since this introduces the possibility of mutual recursion. * Made normal forms self-contained. * Use unique ids, not content hashes, for content referencing.
2003-07-14 * After building, scan for actual file system references asEelco Dolstra1-3/+3
opposed to declared references. This prunes the reference graph, thus allowing better garbage collection and more efficient derivate distribution.
2003-07-10 * A command to register successor fstate expressions.Eelco Dolstra1-0/+3
Unifying substitutes and successors isn't very feasible for now, since substitutes are only used when no path with a certain is known. Therefore, a normal form of some expression stored as a substitute would not be used unless the expression itself was missing.
2003-07-10 * The policy-free derivate sharing now *almost* works. :-) For anyEelco Dolstra1-0/+2
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-09 * When computing the set of paths referenced by an expression, alsoEelco Dolstra1-4/+8
include the paths of the subterms.
2003-07-08 * A command to query the paths referenced by an fstate expression.Eelco Dolstra1-1/+12
* Use a temporary directory for build actions.
2003-07-07 * Refactoring on the file names.Eelco Dolstra1-0/+80