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)
30 lines
786 B
Nix
30 lines
786 B
Nix
with import ./config.nix;
|
|
|
|
rec {
|
|
|
|
printRefs =
|
|
''
|
|
echo $exportReferencesGraph
|
|
while read path; do
|
|
read drv
|
|
read nrRefs
|
|
echo "$path has $nrRefs references"
|
|
echo "$path" >> $out
|
|
for ((n = 0; n < $nrRefs; n++)); do read ref; echo "ref $ref"; test -e "$ref"; done
|
|
done < refs
|
|
'';
|
|
|
|
foo."bar.runtimeGraph" = mkDerivation {
|
|
name = "dependencies";
|
|
builder = builtins.toFile "build-graph-builder" "${printRefs}";
|
|
exportReferencesGraph = ["refs" (import ./dependencies.nix {})];
|
|
};
|
|
|
|
foo."bar.buildGraph" = mkDerivation {
|
|
name = "dependencies";
|
|
builder = builtins.toFile "build-graph-builder" "${printRefs}";
|
|
exportReferencesGraph = ["refs" (import ./dependencies.nix {}).drvPath];
|
|
};
|
|
|
|
}
|