about summary refs log tree commit diff
path: root/corepkgs/buildenv/builder.pl.in
AgeCommit message (Collapse)AuthorFilesLines
2007-05-02 * Set the right priorities when recovering from a directoryEelco Dolstra1-1/+1
collision.
2007-04-27 * Package conflict resolution through priority levels. If there is aEelco Dolstra1-18/+42
user environment collission between two packages due to overlapping file names, then a package with a higher priority will overwrite the symlinks of a package with a lower priority. E.g., $ nix-env --set-flag priority 5 gcc $ nix-env --set-flag priority 10 binutils gives gcc a higher priority than binutils (higher number = lower priority).
2007-04-27 * Allow conflicting packages to be kept in a user environment, andEelco Dolstra1-3/+8
allow switching between them (NIX-80). Example: two versions of Pan: $ nix-env -q pan pan-0.128 pan-0.14.2.91 $ readlink $(which pan) /nix/store/l38jrbilw269drpjkx7kinhrxj6fjh59-pan-0.14.2.91/bin/pan At most one of them can be active any given time. Assuming than 0.14.2.91 is active, you can active 0.128 as follows: $ nix-env --set-flag active false pan-0.14.2.91 $ nix-env --set-flag active true pan-0.128 $ readlink $(which pan) /nix/store/nziqwnlzy7xl385kglxhg75pfl5i936n-pan-0.128/bin/pan More flags to follow.
2006-09-25 * Use "propagated-user-env-packages", not "propagated-build-inputs"Eelco Dolstra1-1/+1
for packages that should be propagated to the user environment.
2006-09-25 * Propagated packages now have lower priority; they are symlinkedEelco Dolstra1-14/+39
*after* the packages that have been explicitly installed, and collisions are ignored.
2006-08-22 * Revert unintentional commit.Eelco Dolstra1-1/+1
2006-08-16 * `nix-instantiate --{eval|parse}-only --xml': print an XMLEelco Dolstra1-1/+1
representation instead of an ATerm. * Indent XML output.
2005-07-22 * Adhockery.Eelco Dolstra1-0/+1
2005-03-07 * Automatically add propagated build inputs to user environments.Eelco Dolstra1-1/+15
Maybe this is a bad idea.
2004-10-25 * New language feature: with expressions.Eelco Dolstra1-1/+1
The expression `with E1; E2' evaluates to E2 with all bindings in the attribute set E1 substituted. E.g., with {x = 123;}; x evaluates to 123. That is, the attribute set E1 is in scope in E2. This is particularly useful when importing files containing lots definitions. E.g., instead of let { inherit (import ./foo.nix) a b c d e f; body = ... a ... f ...; } we can now say with import ./foo.nix; ... a ... f ... I.e., we don't have to say what variables should be brought into scope.
2004-09-19 * prevent collision on log directoryNiels Janssen1-1/+2
2004-04-06 * Make the creation of user environments much faster and more storageEelco Dolstra1-45/+66
efficient by creating only a single symlink to entire directory trees unless a collission occurs.
2004-03-15 * Make perl a dependency of Nix.Eelco Dolstra1-0/+72