nix/tests/functional/lang/eval-fail-addDrvOutputDependencies-multi-elem-context.err.exp

error:
       … while calling the 'addDrvOutputDependencies' builtin
         at /pwd/lang/eval-fail-addDrvOutputDependencies-multi-elem-context.nix:18:4:
           17|
           18| in builtins.addDrvOutputDependencies combo-path
             |    ^
           19|

       error: context of string '/nix/store/pg9yqs4yd85yhdm3f4i5dyaqp5jahrsz-fail.drv/nix/store/2dxd5frb715z451vbf7s8birlf3argbk-fail-2.drv' must have exactly one element, but has 2
Add `builtins.addDrvOutputDependencies` End goal: make `(mkDerivation x).drvPath` behave like a non-DrvDeep context. Problem: users won't be able to recover the DrvDeep behavior when nixpkgs makes this change. Solution: add this primop. The new primop is fairly simple, and is supposed to complement other existing ones (`builtins.storePath`, `builtins.outputOf`) so there are simple ways to construct strings with every type of string context element. (It allows nothing we couldn't already do with `builtins.getContext` and `builtins.appendContext`, which is also true of those other two primops.) This was originally in #8595, but then it was proposed to land some doc changes separately. So now the code changes proper is just moved to this, and the doc will be done in that. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com> Co-authored-by: Théophane Hufschmitt <7226587+thufschmitt@users.nore github.com> Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io 2023-10-23 15:15:52 +00:00			`error:`
			`… while calling the 'addDrvOutputDependencies' builtin`
			`at /pwd/lang/eval-fail-addDrvOutputDependencies-multi-elem-context.nix:18:4:`
			`17\|`
			`18\| in builtins.addDrvOutputDependencies combo-path`
			`\| ^`
			`19\|`

			`error: context of string '/nix/store/pg9yqs4yd85yhdm3f4i5dyaqp5jahrsz-fail.drv/nix/store/2dxd5frb715z451vbf7s8birlf3argbk-fail-2.drv' must have exactly one element, but has 2`