about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2005-05-07 * Don't try to register GC roots in read-only mode.Eelco Dolstra1-2/+2
2005-05-04 * Include some required header files.Eelco Dolstra3-1/+4
2005-05-04 * FreeBSD 4.x doesn't have stdint.h, use inttypes.h instead (which isEelco Dolstra3-3/+3
also part of ISO C).
2005-05-04 * Idem (constness fix).Eelco Dolstra1-2/+2
* `compare' in GCC 2.95 is broken.
2005-05-04 * GCC 2.95 compatibility fix in constness; strangely, I think thisEelco Dolstra1-1/+1
should not have worked at all.
2005-05-04 * GCC 2.95 compatibility. Prevents internal compiler error in memberEelco Dolstra2-2/+2
template friends.
2005-05-04 * The eof() state isn't guaranteed to be set non-lazily. GCC 2.95Eelco Dolstra1-1/+1
compatibility fix.
2005-05-02 * Merging from nix-make branch:Eelco Dolstra1-6/+40
- Add __currentTime primitive (dangerous!). - Allow imports of derivations.
2005-04-13 * Remove redundant message.Eelco Dolstra1-4/+0
2005-04-12 * Garbage collector fix: allow deletion of paths that have invalidEelco Dolstra1-4/+4
(but substitutable) referers.
2005-04-11 * Slightly nicer message.Eelco Dolstra1-3/+3
2005-04-10 * Primop `__currentSystem' to return the current platform identifier.Eelco Dolstra2-9/+14
2005-04-08 * nix-store: `--substitute' -> `--register-substitutes'.Eelco Dolstra2-4/+4
2005-04-08 * Make `nix-store --query --tree' work on non-derivations (i.e., onEelco Dolstra1-15/+13
any store path).
2005-04-07 * If store paths are specified as sources in Nix expressions, don'tEelco Dolstra1-8/+18
copy them, but use them directly.
2005-04-07 * Support base-32 hash representations.Eelco Dolstra1-2/+6
2005-04-07 * `nix-store --add-fixed' to preload the outputs of fixed-outputEelco Dolstra4-15/+117
derivations. This is mostly to simplify the implementation of nix-prefetch-{url, svn}, which now work properly in setuid installations. * Enforce valid store names in `nix-store --add / --add-fixed'.
2005-03-26 * Re-enable dot graph generation.Eelco Dolstra2-34/+44
2005-03-25 * When finding live paths, the deriver need not be valid.Eelco Dolstra1-1/+4
2005-03-25 * `nix-store --verify': repair bad referer mappings.Eelco Dolstra1-6/+16
2005-03-24 * Create missing log and temproots directories automatically (reportedEelco Dolstra4-13/+25
by Rob).
2005-03-23 * Fix endianness bug.Eelco Dolstra1-18/+18
2005-03-23 * Export the references graph to the build hook.Eelco Dolstra1-14/+30
2005-03-23 * `nix-store --register-validity': allow a path to refer to a pathEelco Dolstra3-25/+63
listed later in the list of new valid paths.
2005-03-23 * Canonicalise path meta-data in `nix-store --register-validity'.Eelco Dolstra1-1/+4
2005-03-23 * nix-store: `--isvalid' -> `--check-validity', `--validpath' ->Eelco Dolstra4-17/+34
`--register-validity'. * `nix-store --register-validity': read arguments from stdin, and allow the references and deriver to be set.
2005-03-14 * Bug in clearSubstitutes().Eelco Dolstra1-1/+2
2005-03-10 * Check for duplicate attributes and formal parameters in NixEelco Dolstra1-0/+61
expressions.
2005-03-03 * Don't use fork() in copyPath(), but a string buffer.Eelco Dolstra2-47/+17
2005-03-03 * Increase Berkeley DB limits a bit more.Eelco Dolstra2-7/+26
* Maintain the cleanup invariant in clearSubstitutes().
2005-03-02 * `nix-store -q --hash' to quickly query the hash of the contents of aEelco Dolstra3-6/+28
store path (which is stored in the database).
2005-02-23 * When multiple derivations are specified in `nix-store -r', don'tEelco Dolstra1-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 theEelco Dolstra2-14/+33
NAR dump of the path).
2005-02-22 * Compatibility hack so that Nixpkgs can continue to do hash checkingEelco Dolstra2-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 instantiatedEelco Dolstra1-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-17 * `nix-store -q --tree' shows a tree representing the dependency graphEelco Dolstra2-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 Dolstra1-1/+3
2005-02-17 * Switch to the calling user context for some more operations in aEelco Dolstra2-2/+6
setuid installation.
2005-02-17 * Put build logs in $prefix/var/nix/log/drvs/.Eelco Dolstra1-1/+1
2005-02-15 * Compatibility with older GCCs.Eelco Dolstra1-5/+15
2005-02-15 * And yet another installation source: the ability to copy userEelco Dolstra1-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-14 * It is now possible to add store derivations or paths directly to aEelco Dolstra4-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).
2005-02-14 * Added an installation source `--from-expression' (or `-E') toEelco Dolstra1-8/+22
install derivations from a Nix expression specified on the command line. This is particularly useful for disambiguation if there are multiple derivations with the same name. For instance, in Nixpkgs, to install the Firefox wrapper rather than the plain Firefox component: $ nix-env -f .../i686-linux.nix -i -E 'x: x.firefoxWrapper' The Nix expressions should be functions to which the default Nix expression (in this case, `i686-linux.nix') is passed, hence `x: ...'. This might also be a nice way to deal with high-level (user-level) variability, e.g., $ nix-env -f ./server.nix -i -E 'x: x {port = 8080; ssl = false;}'
2005-02-14 * Refactoring. Hope this doesn't break the semantics of `-u' ;-)Eelco Dolstra3-163/+171
2005-02-14 * Implement the `gc-keep-derivations' global configuretion flag.Eelco Dolstra1-1/+14
2005-02-14 * Global configuration option `env-keep-derivations' to store pointerEelco Dolstra4-34/+52
to derivations in user environments. Nice for developers (since it prevents build-time-only dependencies from being GC'ed, in conjunction with `gc-keep-outputs'). Turned off by default.
2005-02-14 * Don't keep the derivation symlink when creating profile generations.Eelco Dolstra1-11/+6
2005-02-14 * Type error in constructor call (caught by GCC 3.3, but not 3.4!).Eelco Dolstra1-1/+1
2005-02-11 * Refactoring to support different installation sources in nix-env.Eelco Dolstra5-61/+125
* Set the references for the user environment manifest properly. * Don't copy the manifest (this was accidental). * Don't store derivation paths in the manifest (maybe this should be made optional). This cleans up the semantics of nix-env, which were weird. * Hash on the output paths of activated components, not on derivation paths. This is because we don't know the derivation path of already installed components anymore, and it allows the installation of components by store path (skipping Nix expressions entirely). * Query options `--out-path' and `--drv-path' to show the output and derivation paths of components, respectively (the latter replaces the `--expr' query).
2005-02-11 * Input sources should be in the set of all referenceable paths too.Eelco Dolstra2-6/+6