Subject: Re: bug#32339: Nix import

From: Ludovic Courtès <[email-masked]>
Date: Fri, 21 Jun 2019 17:06:09 +0200

Hello,

Andreas Enge <[email-masked]> skribis:

> Omitting the "--strict" flag is not a solution, since then lazy evaluation
> leads to most interesting fields of the result being empty (the return string
> value is "<CODE>").

Do we know exactly why Nix stack-overflows?  Perhaps we’re evaluating
fields we shouldn’t evaluate?

It used to work :-), so something must have changed in the Nix
evaluation rules or in how Nixpkgs attribute sets are written.  We
should ask the Nix folks for guidance.

Ludo’.