30dcc19d1f
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ``` (cherry picked from commit 68c81c737571794f7246db53fb4774e94fcf4b7e)
27 lines
453 B
Nix
27 lines
453 B
Nix
with import ./config.nix;
|
|
|
|
let
|
|
|
|
bar = mkDerivation {
|
|
name = "bar";
|
|
builder = builtins.toFile "builder.sh"
|
|
''
|
|
echo 'builtins.add 123 456' > $out
|
|
'';
|
|
};
|
|
|
|
value =
|
|
# Test that pathExists can check the existence of /nix/store paths
|
|
assert builtins.pathExists bar;
|
|
import bar;
|
|
|
|
in
|
|
|
|
mkDerivation {
|
|
name = "foo";
|
|
builder = builtins.toFile "builder.sh"
|
|
''
|
|
echo -n FOO${toString value} > $out
|
|
'';
|
|
}
|