<virus_dave>
heyas - are there any docs on how hydra builds darwin stuff? Like, what's the production setup look like? Who's hosting the machines? etc?
<gchristensen>
virus_dave: I can help in like 30min
<virus_dave>
thanks
nikivi has joined #nix-darwin
<gchristensen>
virus_dave: we own 10(9?) mac minis all running NixOS, with macOS running in qemu
<virus_dave>
oh interesting, so you really do use physical macs that you own. Rats, i was hoping to hear that there was a cloud-friendly way you'd found to accomplish this :(
<gchristensen>
theoretically it would be possible to apply the same technique to non-mac-mini hardware
<gchristensen>
but you sort of get in to a weird question about if you're following the eula, and if you care
<virus_dave>
ah interesting. i guess that makes sense
<virus_dave>
actually have a pair of use cases which are morally equivalent; one is "shared nix cache we want to populate with darwin builds" (exactly the Darwin Hydra case) and the other is "shared $OTHER_BUILD cache we want to populate with darwin builds". I was hoping there was a good answer to the former that would more-or-less be a drop in for both
<virus_dave>
this is a good start for me though
<gchristensen>
cool
<gchristensen>
are you doing some sort of malware research? :)
<virus_dave>
ah, no. it's litterally "
<virus_dave>
"caching build artifacts" in both cases
<gchristensen>
cool
virus_dave has quit [Quit: virus_dave]
eraserhd has quit [Quit: WeeChat 2.7.1]
eraserhd has joined #nix-darwin
eraserhd has quit [Client Quit]
eraserhd has joined #nix-darwin
philr has quit [Ping timeout: 240 seconds]
hmpffff has quit [Quit: nchrrrr…]
eraserhd has quit [Quit: WeeChat 2.8]
eraserhd has joined #nix-darwin
eraserhd has quit [Client Quit]
eraserhd has joined #nix-darwin
eraserhd has quit [Ping timeout: 240 seconds]
hmpffff has joined #nix-darwin
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
cransom has quit [Quit: WeeChat 2.6]
cransom has joined #nix-darwin
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
__monty__ has quit [Quit: leaving]
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
mbrgm_ has joined #nix-darwin
mbrgm has quit [Ping timeout: 265 seconds]
mbrgm_ is now known as mbrgm
philr has joined #nix-darwin
<abathur>
curious what others' experiences are with nix-shell pure and bashrc/profile creeping in? I'm not sure if this is general, or unique to macos's odd relationship with the startup files and my own handling
<abathur>
which honestly isn't all that bad for most human use, but was a little frustrating when I was *trying* to get a clean environment to fiddle with sourcing a profile script without anything else interfering...
<abathur>
for context, I've set my ~/.bash_profile on macOS to just source ~/.bashrc