self reply
self reply
in reply to Daniel Barlow
in reply to Trolli Schmittlauch :sloth:
in reply to Daniel Barlow
in reply to Trolli Schmittlauch :sloth:

@schmittlauch@toot.matereal.eu I expect that's the path I will take, but given that the package I want to use (net-mqtt) is marked broken in nixpkgs, I think it's some way off.

Look, I get the whole "free-software keep-both-parts-if-you-break-it get-what-you-paid-for" thing, I've been involved in free software since before Linux was 1.0 and I've been running (and writing stuff for) Nix systems for a few years too, so I'm not demanding that anyone stop what they're doing and fix my shit for free. I'm just a bit surprised at the apparent lack of polish in an area that I thought was a focus for a non-zero number of Nix folk.

self reply

also (full disclosure) I am tired and cranky because it's almost midnight and so is my 2yo child, and there is also something wrong with my mqtt broker or the way I expect it to work because it seems to be dropping all my test messages on the floor.

in reply to Daniel Barlow
in reply to erictapen

@erictapen @dan I’m using it without any unexpected issues here for more than five years.

net-mqtt is marked as broken. Nix (or Stackage) doesn’t fix unmaintained packages. Someone else needs to fix them when devs don’t have time to do it (especially during GHC bump).

I used Haskell from cabal, stack, cabal new*, pacman (habs), debian and so on. If you find Haskell on Nix/Guix not optimal then try other options and wait for a GHC bump ;)

self reply