| 23 May 2021 |
 sterni | but looked like a genuine bug to me as well | 03:30:27 |
 joe | It's already on Hackage! | 03:30:52 |
| sterni | ah, awesome :) should've subscribed to the PR's notifications then | 03:31:10 |
| joe | Also: "I am upstream hnix" (in part of course) | 03:31:20 |
| sterni | I see, wasn't aware. | 03:51:17 |
| joe | is peti still doing things, I notice he's no longer a suggested review | 04:47:53 |
| joe | * is peti still doing things? I notice he's no longer a suggested reviewer | 04:48:01 |
|  meck joined the room. | 06:53:27 |
 cdepillabout | In reply to @joe:monoid.al
is peti still doing things? I notice he's no longer a suggested reviewer No, he stepped down a few weeks ago: https://discourse.nixos.org/t/im-retiring-from-haskell-maintenance-in-nixpkgs/12739 | 08:36:08 |
| joe | good for him :) he's earned it! | 08:38:02 |
 maralorn | Huh, that is another solution for the problem we discussed yesterday. I wonder if we can write a convenient helper for that … https://github.com/NixOS/nixpkgs/pull/124099 | 10:38:31 |
|  V joined the room. | 11:21:19 |
| joe | oh, that's nice | 12:12:57 |
| maralorn | cdepillabout: I have ticked of all my build errors on haskell-updates. Most of them were weird false positives. | 12:19:52 |
| cdepillabout | In reply to @maralorn:maralorn.de
cdepillabout: I have ticked of all my build errors on haskell-updates. Most of them were weird false positives. Thanks! I'm waiting to do another ping-maintainers, but Hydra just won't finish those darwin builds. There are still about 6700 left. | 12:21:34 |
| maralorn | Yeah, well it’s a time of high activity. | 12:22:30 |
| maralorn | (Doing a whole communication platform switch exactly during branch-off is kinda crazy if you think about it …) | 12:23:10 |
 pennae | but it..worked? :D | 12:24:14 |
 pwmosquito | Hey all, here's a shameless plug for my little skeleton i use for my haskell projects:
https://github.com/pwm/nixkell
I used to copy&paste various nix bits from project to project and one day I decided to package it all up and put it up on gh. Hope some will find it useful. Any feedback/criticism welcome :) | 13:02:26 |
| pwmosquito | PS: it's probably most useful for nix beginners and I've tried to write the readme with that in mind | 13:04:22 |
| maralorn | pwmosquito: Cool. | 13:06:59 |
| maralorn | Although I personally when I start with something find it hard to understand all the stacking abstractions. So I am not convinced of the additional toml file. | 13:09:01 |
| maralorn | But I am sure it’s convenient when you know how it works. | 13:09:40 |
| maralorn | pwmosquito: What are the nicest conveniences when using hpack instead of directly writing the cabal file? | 13:12:10 |
| pwmosquito | Hey maralorn ,
Re toml config - I thought that haskellers who are not (yet) familiar with nix will find it easy to do stuff in the toml config (ghc version, nix env tools). Once they are more comfortable with nix they can ofc do whatever, eg. get rid of the toml config :) | 13:14:21 |
| joe | My copypaste file is just
{ nixpkgsSrc ? <nixpkgs>, pkgs ? import nixpkgsSrc { }, compiler ? null }:
let
haskellPackages = if compiler == null then
pkgs.haskellPackages
else
pkgs.haskell.packages.${compiler};
in haskellPackages.developPackage {
name = "";
root = pkgs.nix-gitignore.gitignoreSource [ ] ./.;
}
| 13:14:41 |
| pwmosquito | Re hpack - simply personal preference, i never actually learnt the cabal syntax :D I just write yaml and let hpack deal with the bespoke syntax of cabal | 13:15:08 |
| joe | In reply to @maralorn:maralorn.de
pwmosquito: What are the nicest conveniences when using hpack instead of directly writing the cabal file? I use hpack solely for being able to not have to list out all the files, (and being able to have common settings shared between several targets, although I think cabal has this now?) | 13:15:56 |
| joe | and the documentation is imho clearer | 13:16:37 |
| joe | * and the documentation is imho clearer, although an understanding of cabal is also necessary I guess | 13:16:53 |
