| 10 May 2025 |
 maralorn | On the other hand most community channels include nixos in their name | 17:03:50 |
| maralorn changed the room name to "Haskell in nixpkgs" from "Haskell in nixpkgs / on nixos". | 17:04:38 |
| maralorn | Let's try it this way | 17:05:22 |
| maralorn | I guess valuing preciseness over newcomer friendliness is a Haskell trademark... | 17:06:17 |
| maralorn changed the room name to "Haskell in Nixpkgs/NixOS" from "Haskell in nixpkgs". | 17:19:36 |
 John Wiegley | So true, so true... | 17:27:06 |
| John Wiegley | Now I have to find where to report this, thanks for the help and pointers! | 17:27:35 |
| 11 May 2025 |
 cdepillabout | There's a question on discourse about why the latest version of Haskell packages isn't always used in nixpkgs: https://discourse.nixos.org/t/packaging-prebuilt-haskell-binaries/64031 | 00:33:00 |
| cdepillabout | It seems like no one really knowledgeable about the situation has replied yet. Maybe someone from here would be able to explain better what is going on. | 00:33:36 |
|  loudgolem joined the room. | 02:41:57 |
|  Funky changed their profile picture. | 05:29:12 |
 Janus | In reply to @cdepillabout:matrix.org
It seems like no one really knowledgeable about the situation has replied yet. Maybe someone from here would be able to explain better what is going on. i think Daniel firth covered the underlying concepts well on the nix full time Podcast mentioned in the thread | 06:05:09 |
| cdepillabout | Ah good to know! I'll have to give that a listen | 07:15:16 |
| maralorn | Ill reply latter today. | 07:48:46 |
| maralorn | sterni: I polished https://md.darmstadt.ccc.de/s/jQOOTFHLs# and intend to post it now. I realize that it is currently undecided on the minor version front. | 19:50:41 |
| maralorn | https://discourse.nixos.org/t/nixpkgs-ghc-deprecation-policy-user-feedback-necessary/64153 | 19:57:53 |
| maralorn | My plan is to settle this before the release of 25.05 so that we can add the deprecation to the release notes and drop them right after that. | 19:58:40 |
| maralorn | * My plan is to settle this before the release of 25.05 so that we can add the deprecation to the release notes. | 19:59:01 |
 hellwolf | First time I use cabal2nix / callPackage to package my local project... | 20:45:33 |
| hellwolf | Basic question: how can I skip tests of all my dependencies, just like what cabal build would do? | 20:45:54 |
| hellwolf | Currently, some packages failed to evaluate due to test, e.g., crypton. | 20:46:10 |
 alexfmpe | dontCheck util | 21:01:55 |
| hellwolf | how do I apply to all dependencies automatically? | 21:04:19 |
| hellwolf | I guess doing a map over "pkgs.haskell.packages.${ghcId}" setting "donCheck = true" would be an overkill? | 21:21:41 |
 WeetHet | @maralorn:maralorn.de re: packaging latest versions, would defining a package in by-name also work or will there be a conflict between the two? | 21:22:30 |
| WeetHet | In reply to @hellwolf:matrix.org
I guess doing a map over "pkgs.haskell.packages.${ghcId}" setting "donCheck = true" would be an overkill? mkDerivation = args: hprev.mkDerivation ({ doCheck = false; } // args | 21:26:03 |
| WeetHet | This is what I've done, I don't like it but it works | 21:26:26 |
| hellwolf | yikes :) | 21:29:48 |
| hellwolf | but I realized it was largely my own fault of tracking ghc 9.12.2 already.. only package is broken without a cache is crypton, I will just apply a hack for that package alone. | 21:30:41 |
| maralorn | In reply to @weethet:catgirl.cloud
@maralorn:maralorn.de re: packaging latest versions, would defining a package in by-name also work or will there be a conflict between the two? Well, it is generally possible to package haskell packages in by-name. But it is unclear to me what that's supposed to solve. | 21:34:50 |
