5 lines
395 B
Markdown
5 lines
395 B
Markdown
|
How can I interrogate a Nix builder?
|
||
|
|
|
||
|
|
Nix derivations are often horrifyingly difficult to read. It is also difficult to figure out how to wrangle Nix into giving up any information about how it's interpreting the derivation.
|
||
|
|
|
||
|
|
In order to understand these tools that I'm working with, I need to be able to inject the equivalent of debug prints and have a very clear place to get the results back.
|