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)
24 lines
599 B
Nix
24 lines
599 B
Nix
{ altitude, storeFun }:
|
|
|
|
with import ../config.nix;
|
|
|
|
mkDerivation {
|
|
name = "nested-sandboxing";
|
|
busybox = builtins.getEnv "busybox";
|
|
EXTRA_SANDBOX = builtins.getEnv "EXTRA_SANDBOX";
|
|
buildCommand = if altitude == 0 then ''
|
|
echo Deep enough! > $out
|
|
'' else ''
|
|
cp -r ${../common} ./common
|
|
cp ${../common.sh} ./common.sh
|
|
cp ${../config.nix} ./config.nix
|
|
cp -r ${./.} ./nested-sandboxing
|
|
|
|
export PATH=${builtins.getEnv "NIX_BIN_DIR"}:$PATH
|
|
|
|
source common.sh
|
|
source ./nested-sandboxing/command.sh
|
|
|
|
runNixBuild ${storeFun} ${toString altitude} >> $out
|
|
'';
|
|
}
|