| 25 May 2026 |
Ember | will have to try this again soon | 23:11:45 |
| 26 May 2026 |
alexfmpe | Ah yeah jsaddle-warp didn't work on firefox | 06:25:25 |
alexfmpe | I think it's supposed to work nowadays? | 06:25:44 |
| phanirithvij changed their display name from loudgolem to phanirithvij. | 11:40:40 |
sterni | The question is of course what to do about master which is going to become 26.05. We've patched some packages so they work with the deprecated Hakyll version, but it's probably annoying to ship it. | 16:50:08 |
sterni | Not sure which way to go is easier though, probably reverting the update | 16:50:17 |
Artem | not an expert, but for me personally reverting makes the most sense | 18:50:21 |
| 28 May 2026 |
| magnolia_mayhem changed their display name from Mr Mayhem's Dumbass Labradoodle to magnolia_mayhem. | 04:48:27 |
| Akshay Sachdeva set a profile picture. | 05:30:26 |
alexfmpe | Huh, am I very confused or are we doing builds without optimization? GHC manual says -O0 is the default and I don't see -O1 being set in
https://downloads.haskell.org/ghc/latest/docs/users_guide/flags.html#optimisation-levels | 10:40:21 |
alexfmpe | Surely that can't be the case? | 10:40:34 |
alexfmpe | Hmm cabal itself seems to default to -O1 | 10:41:47 |
alexfmpe | So our cabal v1 builder must be using that | 10:42:12 |
| 29 May 2026 |
| lassulus changed their profile picture. | 07:06:19 |
sterni | Alex: https://hydra.nixos.org/build/329119235/nixlog/2 | 10:48:51 |
Alex | Was that the result of a Hackage bump? | 11:01:36 |
Alex | Ok, found the commit (it was). | 11:04:03 |
alexfmpe | In reply to @alexfmpe:matrix.org Hmm cabal itself seems to default to -O1 Actually... would it make sense for us to use -O2 by default? | 17:01:12 |
alexfmpe | I'm not sure exactly how much that slowdowns compilation and don't know the benefit for cpu/memory what with ghc not doing whole-program optimization, but it might also decrease binary size which is a win on nixpkgs, hydra etc? | 17:03:28 |
alexfmpe | wonder if just building cabal itself with -O2 would make compiling everything else faster enough that it pays for itself | 17:04:52 |
teo (they/he) | Often -O2 is not worth it | 17:07:52 |
teo (they/he) | It's the sort of thing that should be benchmarked on a case by case basis | 17:08:41 |
teo (they/he) | Redacted or Malformed Event | 17:08:42 |
| 31 May 2026 |
whispers [& it/fae] | hii! i have a procedural haskellPackages question. i have a few packages i'd eventually like to mark broken (haskellPackages.gi-soup2, haskellPackages.spike) because they depend on the libsoup_2_4, and i'd like to get rid of that (not yet, but planning to look into it soon). the dependency is defined in hackage-packages.nix, but aiui that's not something you're supposed to touch directly. where in nixpkgs would i (a) drop the dependency on the system library so that we don't get eval failures, and (b) mark it as broken? i'm looking through the manual and haskell-modules/HACKING.md but can't find anything that seems immediately relevant | 01:35:33 |
whispers [& it/fae] | hii! i have a procedural haskellPackages question. i have a few packages i'd eventually like to mark broken (haskellPackages.gi-soup2, haskellPackages.spike) because they depend on the libsoup_2_4 derivation, and i'd like to get rid of that (not yet, but planning to look into it soon). the dependency is defined in hackage-packages.nix, but aiui that's not something you're supposed to touch directly. where in nixpkgs would i (a) drop the dependency on the system library so that we don't get eval failures, and (b) mark it as broken? i'm looking through the manual and haskell-modules/HACKING.md but can't find anything that seems immediately relevant | 02:02:58 |
alexfmpe | probably https://github.com/NixOS/nixpkgs/blob/haskell-updates/pkgs/development/haskell-modules/configuration-common.nix | 13:33:21 |
alexfmpe | or configuration-nix.nix, if it's due to nix(pkgs) specific reasons, rather than general distro things | 13:34:19 |
sterni | if the library is removed, the dependency will also be removed on the next regeneration. | 14:03:46 |
sterni | libs can be marked broken in the generator's configuration | 14:04:37 |
aiya | Redacted or Malformed Event | 17:44:16 |