| 13 Mar 2025 |
 puck | In reply to @puck:puck.moe
they are values derived from either the current drv's output, or any input drv + its output. its representation is / then the nixbase32 repr of the full sha256 of either "nix-output: " or "nix-upstream-output: :<the name the output would have; so either drv's name or append a dash and the output name>" uh, one colon. element's not letting me edit this message :v | 16:42:22 |
 jade_ | NIX_REMOTE | 20:41:29 |
| jade_ | its really badly documented but it is actually equivalent to --store internally; see my hastily scrawled notes on all env-vars used by cppnix derivatives https://docs.lix.systems/manual/lix/stable/contributing/testing.html?highlight=NIX_REMOTE#used-by-lix | 20:42:58 |
 John Ericson | You can also use just use NIX_CONFIG, the one env var to rule them all | 20:48:09 |
| jade_ | mhm | 20:49:55 |
| jade_ | it seems like sometimes env-vars get introduced like NIX_ABORT_ON_WARN which should just be more NIX_CONFIG | 20:51:35 |
| John Ericson | If they correspond to an option, yes | 20:55:44 |
| John Ericson | Btw, you should see what we just did to derivation goal | 20:55:58 |
| John Ericson | Even if you're gonna rewrite it in Rust anyways | 20:56:06 |
| 14 Mar 2025 |
| jade_ | yeah, NIX_ABORT_ON_WARN does, i am not sure why it was added; we caught this in code review of builtins.warn | 00:04:27 |
