| 13 Aug 2025 |
 sterni | Artem: ah I think this is a Cabal bug where it doesn't add the tool to PATH and Nix won't do it because it's from the same package, but I'd need to check | 21:40:33 |
 Artem | it sounds like that. I'll grep for the PATH trick. | 21:43:20 |
| 14 Aug 2025 |
| sterni | Artem: I guess it is not a bug, actually. build-tool-depends is only available while building, but during test execution it doesn't have to/shouldn't be. | 00:38:18 |
| Artem | Ah, interesting | 00:48:44 |
| Artem | sterni: funny enough, the documentation for BTD seems to bless this usage:
A list of Haskell executables needed to build this component. Executables are provided during the whole duration of the component, so this field can be used for executables needed during test-suite as well.
https://cabal.readthedocs.io/en/3.16/cabal-package-description-file.html#pkg-field-build-tool-depends
| 01:03:13 |
| sterni | nevermind then… | 01:06:46 |
| Artem | but there might be a bug in that Cabal the library can't handle BTD correctly. I f memory serves, it was primarily cabal-install feature. There may be a ticket on Cabal's bug tracker... | 01:12:37 |
| Artem | the docs proceed to say that "old-style-builds" (which is what you get with the library, so this includes the Nixpkgs Haskell builder) can't handle external deps in BTD, but internal ones should be OK, which is not what we're seeing | 01:15:38 |
| Artem | the PATH trick looks straightforward in the examples I see but it's not working so far with the old result ("fixpoint not found"). I'm investigating it | 01:29:36 |
