Age | Commit message (Collapse) | Author | Files | Lines |
|
So all these years I was totally deluded about the meaning of "set
-e". You might think that it causes statements like "false && true" or
"! true" to fail, but it doesn't...
|
|
|
|
If the options gc-keep-outputs and gc-keep-derivations are both
enabled, you can get a cycle in the liveness graph. There was a hack
to handle this, but it didn't work with multiple-output derivations,
causing the garbage collector to fail with errors like ‘error: cannot
delete path `...' because it is in use by `...'’. The garbage
collector now handles strongly connected components in the liveness
graph as a unit and decides whether to delete all or none of the paths
in an SCC.
|
|
|
|
Since it's rarely used and fixing it is too much work right now,
just document it.
|
|
multiple outputs, but good to have anyway.
|
|
currently fails in read-only mode.
|
|
segfaults.
|
|
recursive outputs are properly rejected.
* Add a (also failing) test for "nix-build -A <output-name>".
|
|
|
|
|
|
This currently fails. Yay test-driven development!
|