Commit 6b18b3d6 authored by Winter's avatar Winter
Browse files

ci/eval: allow configuration of the system to eval attrpaths on 

Right now, there are some paths that don't even get exposed to certain
systems (notably Darwin, but some outliers exist for Linux such as the
Darwin-specific Hackage overlay) for one reason or another, usually
because of assertions like `stdenv.isLinux`. To catch these scenarios,
this change implements a way to specify the system to evaluate attrpaths
on, and makes it default to the system that we're evaluating outpaths
for.
parent 866fbece

ci/eval/default.nix

+5 −1
Original line number Diff line number Diff line
@@ -36,6 +36,9 @@ let 
  supportedSystems = builtins.fromJSON (builtins.readFile ../supportedSystems.json);



  attrpathsSuperset =

    {

      evalSystem,

    }:

    runCommand "attrpaths-superset.json"

      {

        src = nixpkgs;
@@ -55,6 +58,7 @@ let 
            -I "$src" \

            --option restrict-eval true \

            --option allow-import-from-derivation false \

            --option eval-system "${evalSystem}" \

            --arg enableWarnings false > $out/paths.json

      '';
@@ -65,7 +69,7 @@ let 
      # because `--argstr system` would only be passed to the ci/default.nix file!

      evalSystem,

      # The path to the `paths.json` file from `attrpathsSuperset`

      attrpathFile ? "${attrpathsSuperset}/paths.json",

      attrpathFile ? "${attrpathsSuperset { inherit evalSystem; }}/paths.json",

      # The number of attributes per chunk, see ./README.md for more info.

      chunkSize,

      checkMeta ? true,