68c81c7375
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/ ```
34 lines
850 B
Nix
34 lines
850 B
Nix
with import ./config.nix;
|
|
|
|
let innerName = "foo"; in
|
|
|
|
mkDerivation rec {
|
|
name = "${innerName}.drv";
|
|
SHELL = shell;
|
|
|
|
requiredSystemFeatures = [ "recursive-nix" ];
|
|
|
|
drv = builtins.unsafeDiscardOutputDependency (import ./text-hashed-output.nix).hello.drvPath;
|
|
|
|
buildCommand = ''
|
|
export NIX_CONFIG='experimental-features = nix-command ca-derivations'
|
|
|
|
PATH=${builtins.getEnv "EXTRA_PATH"}:$PATH
|
|
|
|
# JSON of pre-existing drv
|
|
nix derivation show $drv | jq .[] > drv0.json
|
|
|
|
# Fix name
|
|
jq < drv0.json '.name = "${innerName}"' > drv1.json
|
|
|
|
# Extend `buildCommand`
|
|
jq < drv1.json '.env.buildCommand += "echo \"I am alive!\" >> $out/hello\n"' > drv0.json
|
|
|
|
# Used as our output
|
|
cp $(nix derivation add < drv0.json) $out
|
|
'';
|
|
__contentAddressed = true;
|
|
outputHashMode = "text";
|
|
outputHashAlgo = "sha256";
|
|
}
|