| 13 Aug 2025 |
 Alyssa Ross | But it's the test suite that runs the binary | 18:18:49 |
 emily | (testing it against the build platform Z3 is strictly less realistic for testing whether the thing you are building will actually work) | 18:18:50 |
| Alyssa Ross | Not the program itself | 18:18:54 |
| Alyssa Ross | Is what we were told | 18:18:56 |
| emily | yeah, and the test suite runs on the host platform | 18:18:59 |
| emily | via the magic of canExecute | 18:19:08 |
| emily | it's testing a host platform thing | 18:19:14 |
| emily | not a build platform thing | 18:19:17 |
| Alyssa Ross | Then what would nativeCheckInputs ever be for? | 18:19:29 |
| emily | make test builds a buildPlatform test runner utility that has a binary dependency or something. | 18:19:59 |
| emily | maybe that dependency is GCC that targets hostPlatform so it can dynamically compile some test code before running it or something. | 18:20:18 |
| emily | like I think the same rule of thumb of "tools used by the build system" applies. | 18:21:06 |
| Alyssa Ross | I guess I'd consider test framework part of the build system | 18:21:58 |
| Alyssa Ross | But really it depends for what purpose it's invoking this tool | 18:22:22 |
| Alyssa Ross | Is it to generate test data? If so, build platform | 18:22:29 |
| emily | it's a Haskell library that provides an interface to an SMT solver | 18:22:35 |
| emily | you write Haskell code and it invokes Z3 at runtime to solve SMT things | 18:22:41 |
| emily | if Z3 was a library, it would be a buildInput | 18:22:48 |
| emily | instead it's something you need to wrap on later | 18:22:55 |
| emily | so it's unambiguously a checkInputs case. it's just that checkInputs sucks to use for executables. | 18:23:04 |
| Alyssa Ross | I see! | 18:23:04 |
| Alyssa Ross | Okay, then this is indeed a check input, and testSystemDepends should be fine. | 18:23:31 |
| emily | arguably we should be patching in the path to Z3 in the library code | 18:23:38 |
| emily | in which case there would be no check inputs needed at all | 18:23:47 |
| emily | (and no wrappers needed for downstream users) | 18:23:52 |
| emily | but that might not be desirable. since you might want to use another backend at runtime | 18:24:02 |
| emily | so having it in the closure of smtlib-backends-process is likely suboptimal | 18:24:17 |
| emily | (does GHC cross even work in Nixpkgs…) | 18:24:39 |
 Artem | if I unbreak certain Haskell package (e.g. by adding jailbreaks and alike in configuration-common.nix), do I remove broken=false; from hackage-packages.nix in the same commit that I want to submit as a PR? | 18:28:55 |
| Artem | ah, I guess I update configuration-hackage2nix/broken.yaml, sorry | 18:33:08 |
