!lheuhImcToQZYTQTuI:nixos.org

Nix on macOS

1169 Members
“There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org193 Servers

Load older messages


SenderMessageTime
3 Mar 2026
@samasaur:matrix.orgsamasaur man -wa ln may be helpful? 16:00:00
@antifuchs:asf.computerantifuchsoh, yep, that's the flag. it's the regular built-in manpage. I just got confused by which ln was used in the activation script (:16:01:53
@antifuchs:asf.computerantifuchs (that script uses the coreutils one, which stumbles over -h) 16:02:35
@emilazy:matrix.orgemilyseems like an empty rebrand to me18:22:00
@reckenrode:matrix.orgRandy EckenrodeProbably, but dropping down to only six performance cores doesn’t seem very pro.18:55:49
@sarahec:matrix.orgSarah ClarkIt sounds like they didn't improve the cooling enough so we get a pile of the slower cores19:26:57
@sarahec:matrix.orgSarah ClarkI have a M3 Max and set num-cores to not touch the efficiency cores most of the time. 19:28:02
@reckenrode:matrix.orgRandy EckenrodeI limit the number of simultaneous jobs because otherwise Nix happily schedule way too many simultaneous builds for a workstation.19:29:44
@weethet:catgirl.cloudWeetHetBy the way, did someone investigate the QoS classes in the end?21:09:12
@pjhenning:matrix.orgPJ set a profile picture.23:49:02
4 Mar 2026
@lt1379:matrix.orgLunhttps://github.com/NixOS/nixpkgs/pull/49644502:09:13
5 Mar 2026
@logn:zirco.dev@logn:zirco.dev left the room.02:29:05
@emilazy:matrix.orgemily hexa: do you have any feeling for roughly when Darwin staging queue started being especially bad? I am wondering if it might be https://github.com/NixOS/nixpkgs/pull/442945 (because of the mistake mentioned in https://github.com/NixOS/nixpkgs/pull/490358), though that was a few months ago now 15:04:22
@emilazy:matrix.orgemilyI'm inclined to merge https://github.com/NixOS/nixpkgs/pull/490358 and see if it makes the next cycle less bad, but I probably won't notice one way or the other myself :)15:04:55
@hexa:lossy.networkhexano, sadly not15:05:45
@hexa:lossy.networkhexamaybe vcunat remembers15:06:02
@hexa:lossy.networkhexaI'd say for the last two months I had to reboot macs a few times because they ran full and had stuck jobs15:06:33
@emilazy:matrix.orgemily vcunat? :) 15:07:00
@emilazy:matrix.orgemilyit seems plausible that libc++ hardening could make Clang meaningfully slower or whatever15:07:10
@hexa:lossy.networkhexaanyway, the backlog this time was around 55k packages when linux was finished15:07:36
@hexa:lossy.networkhexaand the machines are doing like 10k per day?15:07:54
@hexa:lossy.networkhexaI think we tend to say the current total capacity is like 30k jobs per day15:08:31
@emilazy:matrix.orgemilyok, I'll merge it and we can see15:11:41
@emilazy:matrix.orgemilycould also just be more jobs appearing constantly and Darwin being some multiplicative factor slower I suppose15:12:15
@lt1379:matrix.orgLunis this a good excuse to pgo&bolt the stdenv clang15:18:13
@emilazy:matrix.orgemilynah, would be bad for reproducibility15:18:49
@lt1379:matrix.orgLunf15:18:55
@hexa:lossy.networkhexai'm like 20% on board with reproducibility being a focus of the project15:19:17
@emilazy:matrix.orgemily stdenv being inherently non-reproducible is certainly not okay 15:21:07
@emilazy:matrix.orgemilyfor leaf packages it's less concerning15:21:17

Show newer messages


Back to Room ListRoom Version: 6