diff options
| author | zimbatm <zimbatm@zimbatm.com> | 2019-11-03 17:40:43 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-03 17:40:43 +0000 |
| commit | 71184f8e157672789602d3f28bdd3c8079800687 (patch) | |
| tree | e5edbe7780c58167826c3ab0e6406ef145ba7111 /pkgs/stdenv/linux | |
| parent | 59edabf8ca74bc8a86f03cabad79bf5a6e272d0a (diff) | |
| download | nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar.gz nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar.bz2 nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar.lz nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar.xz nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.tar.zst nixpkgs-71184f8e157672789602d3f28bdd3c8079800687.zip | |
stdenv/check-meta: getEnv if the attribute is unset (#72376)
There were two issues: * builtins.getEnv was called deep into the nixpkgs tree making it hard to discover. This is solved by moving the call into pkgs/top-level/impure.nix * when the config was explicitly set by the user to false, it would still try and load the environment variable. This meant that it was not possible to guarantee the same outcome on two different systems.
Diffstat (limited to 'pkgs/stdenv/linux')
0 files changed, 0 insertions, 0 deletions