| 2 Jun 2021 |
Las | Well I imagine all packages depend on a specific major version | 13:30:45 |
Las | Since they are often incompatible with each other | 13:30:54 |
maralorn | The question is: Where is the balance between hardcoding that for a certain package or doing it automatically for all packages. | 13:31:51 |
maralorn | Generally doing that for all packages i.e. let them depend on aeson_1_5 and not on aeson would translate a lot of builderrors into eval errors. Also it would bloat nixpkgs by generating a lot of aliases. | 13:35:27 |
maralorn | Still having a way to enable that for some packages would grant us a lot of flexibility … | 13:36:16 |
maralorn | But not even sure if it would solve the haskell-gi problem. | 13:37:16 |
cdepillabout | The Haskell team in Nixpkgs will helping people with hacking on Nix-related stuff at ZuriHac this year. The event is online and free, so we'd love to have everyone here participate if you're free: https://discourse.nixos.org/t/nix-and-haskell-at-zurihac-2021/13417 | 14:14:27 |
Las | It's a shame that ZuriHac isn't also using Matrix | 14:36:57 |
maralorn | Las: I have the fear that Matrix wouldn‘t be able to deliver the same voice/video-chat experience. | 14:38:01 |
Las | maralorn: I don't think that's a fear, that's a fact | 14:40:16 |
Las | Video chat still isn't very well developed on Matrix | 14:40:28 |
Las | For 1-to-1 calls, it's very good though | 14:40:35 |
Las | For multiple people, screen sharing, etc. it's lacking | 14:40:43 |
maralorn | I haven‘t tried for quite a while. | 14:40:47 |
maralorn | Oh, yeah. Screen sharing is probably a pain point. | 14:41:04 |
Las | Jitsi integration is used for it after all | 14:41:32 |
Las | I remember reading on HN some comment by Arathorn about them going to do something about it | 14:42:01 |
Las | But that's probably a few months/years into the future | 14:42:17 |
maralorn | And when I think about how difficult zoom calls with a few dozens of people can be when they have different zoom versions. I am a bit afraid of client diversity in that point. "Please vote with thumbs up. We have 8 different guides in our wiki …" | 14:43:02 |
sterni (he/him) | In light of ZuriHac I wrote up my thoughts on platform handling in hackage2nix: https://github.com/NixOS/cabal2nix/issues/497 I plan to get to this eventually, but maybe someone else is motivated to start to work on it | 14:54:12 |
| bqv changed their display name from bqv to qy. | 14:56:12 |
| bqv changed their display name from qy to bqv. | 14:56:14 |
sterni (he/him) | While writing it up I also realized that my 4th point in the list which was semi-actionable would just disappear if we do the other things which is always good :) | 14:56:30 |
maralorn | I have to admit that I don‘t grasp all details and consequences of it. But it superficially it sounds like a reasonable next step. | 14:58:05 |
sterni (he/him) | I'd be happy to clarify anything / reword the issue if anything is unclear | 14:59:25 |
maralorn | I just don‘t know what meta.badPlatforms is. | 15:00:16 |
sterni (he/him) | maralorn: https://github.com/NixOS/nixpkgs/blob/1834bc871199fc6583cf270474aacbda9e5127f2/pkgs/stdenv/generic/check-meta.nix#L58-L60 | 15:17:13 |
sterni (he/him) | basically if the platform you are trying to build a pkg for is either not in platforms or in badPlatforms it will create an unsupported system error | 15:17:45 |
| dschrempf joined the room. | 15:19:51 |
sterni (he/him) | In reply to @sternenseemann:systemli.org Since builds are getting done now pretty quickly, I'm gonna wait for the darwin builds, then hopefully merge master again later today, hope that in the 1000 commits nothing triggers any major rebuilds and finish this cycle pretty quickly hopefully Merged master, 261 builds to go, so looking good! Hopefully I can merge before I have to help moving this evening. | 15:24:35 |