| 26 Oct 2024 |
 lxsameer | it all started with hasql 1.8 | 14:45:44 |
 maralorn | In reply to @lxsameer:matrix.org
so I can integrate cabal.project.lock, with nix right? Currently only with haskell.nix. | 14:45:59 |
| lxsameer | this is my attempt to fix as I go | 14:46:27 |
| lxsameer | https://git.sr.ht/~lxsameer/Feynman/tree/master/item/flake.nix#L37 | 14:46:29 |
| maralorn | Creating an override set from cabal.project.lock is definitely on my wishlist. | 14:48:17 |
| lxsameer | so the golang and the rust facilicies on nix have a good feature, that you can provide the lock file and a hash for the vendored dependencies. | 14:49:21 |
| lxsameer | I think something like that would be cool for haskell as well | 14:49:46 |
| lxsameer | Unfortunately, I'm not knowledgable enough about haskell stuff to do that; otherwise I would've built something like that | 14:50:22 |
| lxsameer | In reply to @maralorn:maralorn.de
Creating an override set from cabal.project.lock is definitely on my wishlist. did you mean cabal.project.freeze | 15:13:05 |
|  nikkotanns joined the room. | 15:59:07 |
| maralorn | In reply to @lxsameer:matrix.org
did you mean cabal.project.freeze Yes | 15:59:13 |
| maralorn | I guess. | 15:59:29 |
| lxsameer | Cool. I'll try to put something together. Just a quick question: do you know any parser for cabal files? That we might use already | 16:00:32 |
 fgaz | In reply to @lxsameer:matrix.org
Cool. I'll try to put something together. Just a quick question: do you know any parser for cabal files? That we might use already Cabal itself | 16:31:11 |
| fgaz | There are no other complete parsers as far as I know | 16:31:30 |
| fgaz | See also this module if you want to get a PackageDescription out of GenericPackageDescription | 16:34:03 |
| lxsameer | cheers | 17:10:27 |
 sterni (he/him) | In reply to @vigress9:matrix.org
I'm pretty sure you don't need to set LD_LIBRARY_PATH if you use packages instead of buildInputs no, packages is just an alias for nativeBuildInputs which doesn't make a difference for native compilation. Since the headers are in a nonstandard location for C, no standard mechanism of stdenv will pick up on them. | 20:11:37 |
| 27 Oct 2024 |
|  leg7 joined the room. | 10:21:04 |
 emily | hi there, I think I may have accidentally broken GHC on Darwin on staging and I'd like to try and fix it. haskell.compiler.ghc924Binary is failing to build with a Clang-related error – how can I get GHC to print out the Clang command it's running (and its full output, preferably)? | 16:33:59 |
| sterni (he/him) | emily: where is it failing, exactly? ghc924Binary packages a binary version of GHC, so GHC isn't executed a lot. easiest is always to set NIX_DEBUG=1 which prints out the flags passed to cc-wrapper | 23:32:30 |
| emily | I figured it out; it was a bug in the Darwin compiler wrapper code when the environment was empty. NIX_DEBUG=1 doesn't work because you added env -i to check that an empty PATH works 😅 | 23:33:12 |
| emily | which has some other weird side-effects, since it gets rid of all the toolchain-relevant environment variables, including in this case the Darwin SDK. which is nice since it exposed a bug in the fallback SDK logic | 23:33:37 |
| emily | but wonder if it mightn't cause other issues with toolchains that need some kind of set-up in the env to work (cross?) | 23:33:52 |
| 28 Oct 2024 |
 sellout | I just discovered that a Haskell package of mine is marked as broken in Nixpkgs. Turns out I had a fixed version that was sitting on Hackage as an unpublished candidate 🤦🏼 But I was wondering … is there any way to map my GH or Hackage username or something to my Nixpkgs maintainer attribute (they’re all the same), so I can automatically be added as a maintainer on my packages … which, IIRC, means I get notified on Hydra failures, right? | 16:25:50 |
| sterni (he/him) | we don’t have the data of who uploaded the package, so you have to add yourself as a maintainer manually | 16:35:47 |
 pwmosquito | Great, https://github.com/haskell/cabal/pull/8944/commits/6142386198dbe0400b31245cf9c479d3ef692e63 broke using active-repositories: none which for years i've used to tell cabal not to manage package repos. | 16:47:11 |
| pwmosquito | given the above, anyone know what's the current way to tell cabal that i want nix to manage packages? | 16:50:05 |
| pwmosquito | best i could think of is patching cabal-install with
https://github.com/MercuryTechnologies/cabal/commit/ec242b1cb21e450d5212efd5c445f0d70786092e#diff-cb49110a68ba8389eb180bc022e1a59f106a55039a0795acec1f45a66a1ab026L463 | 17:21:57 |
| pwmosquito | which worked | 17:22:01 |
