<arianvp> so what do we think is useful for us?
<arianvp> do we want to let the nixos foundation buy a dev kit? and maybe some other companies with Apple Developer accounts to?
<arianvp> or do we want to get a cloud machine?
<arianvp> I have a feeling physical hardware would make more sense; as we can also experiment with integration with hydra etc
<arianvp> and macstadium might be more limited. I dont know
<thefloweringash> if someone's willing to host it, hardware makes sense to me. IIUC the mac builders are nixos hosts running macOS VMs. getting this configuration going would be trickier without direct access to the boot chain. unless macstadium's remote access also gives full recovery access?
<arianvp> thefloweringash: i dont think that's true. I think we have dedicated Mac Minis
<thefloweringash> FWIW: in my short experiments with the dtk, the x86_64 emulation works well for nix stuff. there's just a small set of tweaks required for big sur installation
<thefloweringash> IIUC they're dedicated mac minis, running nixos, running macos
<arianvp> ah
<thefloweringash> on the topic of big sur and shared library files no longer shiping as .dylibs: the native method of linking appears to be using yaml files in the MacOSX.sdk that describe the contents of the libraries to link against
<thefloweringash> at a glance this seems like it should be sufficient to maintain a pure stdenv by generating appropriate yaml
<thefloweringash> the exact method is left as an exercise to the reader ;-)
<thefloweringash> a quick test of linking using the yaml files from xcode with a nix toolchain seems to work: https://gist.github.com/thefloweringash/7459f96d78ada56708db335d1b6af6c9
<thefloweringash> seems to work on catalina that is, I haven't made a full stdenv
philr_ has quit [Ping timeout: 240 seconds]
eraserhd3 has joined #nix-darwin
eraserhd2 has quit [Ping timeout: 256 seconds]
eraserhd3 has quit [Quit: WeeChat 2.8]
eraserhd has joined #nix-darwin
<infinisil> Hm I'm just trying to manually create the /nix disk such that I can mount it with -o suid as angerman suggested in https://github.com/NixOS/nix/issues/3156
<{^_^}> nix#3156 (by angerman, 39 weeks ago, closed): daemon user fails to install on macOS
<infinisil> After adding nix to synthetic.conf and calling `/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs.util -B` and `sudo diskutil apfs addVolume disk1 APFS 'Nix Store' -mountpoint /nix` I have a /nix
<infinisil> But then I try `sudo mount -o suid /nix`, which gives me the error `mount: /nix: unknown special file or file system.`
<infinisil> And when I try `sudo diskutil mount -o suid /nix`, this gives the error that this is not how diskutils mount is used
<infinisil> I guess the problem here is that I have an APFS volume, but angerman had an HFS one (which presumably worked with just the standard mount)
<infinisil> But then my question is: How can I mount an APFS volume with -o suid?
<{^_^}> #19906 (by copumpkin, 3 years ago, open): Use .tbd files for pure Darwin builds even against impure runtimes
<abathur> arianvp: is it either-or, and do you know if the macstadium access is a fixed resource that org users would be dividing up time on? I can imagine a physical kit being better for a small number of users, but macstadium *might* be useful for more users if the org wasn't being limited to one VM or whatever?
<abathur> infinisil: not sure about this suid stuff, but I didn't see the mkdir command above; any chance it got missed? https://github.com/NixOS/nix/blob/master/scripts/create-darwin-volume.sh#L137
<infinisil> Doesn't appear to be needed
<infinisil> But I think I got it sorted now, I'll post a comment when I verified it actually worked
<abathur> on the off chance it's helpful, I also recall stumbling on this script a few days back when I was looking around to see if anyone had a shell/bash implementation of the system keychain/encryption stuff from shopify, and remember noticing that their setup steps were a little different than the official installer
eraserhd has quit [Quit: WeeChat 2.9]
<infinisil> Oh the enableOwnership thing looks relevant
<infinisil> abathur: Oh awesome that worked too
<abathur> woo; glad that otherwise fruitless search turned up something of value :]
<infinisil> I'm now wondering why this problem happens in the first place, and maybe the installer should take care of this
codyopel has joined #nix-darwin
<abathur> yeah, it would be good to tease out what the difference is
<abathur> especially if the regular installer is doing the wrong thing on end-user systems?
mbrgm_ has joined #nix-darwin
philr_ has joined #nix-darwin
mbrgm has quit [Ping timeout: 264 seconds]
mbrgm_ is now known as mbrgm