{`-`} has joined #nix-darwin
__monty__ has quit [Quit: leaving]
__Sander__ has quit [Quit: Konversation terminated!]
<emily> honestly I think there's enough moving parts involved that it'd probably not be great to retrofit the current Darwin installer into initializing the encryption and and keychain entry and installing the extra LaunchDaemon etc.
<emily> but I guess it's already an overgrown shell script so it might not get too much worse
<antifuchs> hah, very true about the overgrown shell script /:
<gchristensen> yeah :(
<gchristensen> I should have stopped myself the moment I said the words "polymorphic bash script"
<clever> gchristensen: at least your not using webusb to reflash a pi from an android phone, lol: https://github.com/raspberrypi/usbboot/issues/41
<{^_^}> raspberrypi/usbboot#41 (by DimaK-tracxpoint, 1 year ago, open): Any Android ports?
<clever> i probably should have stopped myself way sooner, lol
<das_j> antifuchs: Did you just talk about nixpkgs? ;)
<antifuchs> das_j: I'm confused, where? (:
<das_j> talking about overgrown shell scripts
<clever> das_j: i had a runHaskell function at one point, that had the same api as runCommand
<clever> so your builder could be compiled haskell code
<das_j> bash isn't too bad for usual package building tasks imo. but for stuff like most of the nixos/ tree it's probably not really fitting
<das_j> maybe we should move this to #nixos-chat?
philr has joined #nix-darwin
<LnL> my opinions on a separate installer project are still the same
<LnL> but I don't really have enough time/motivation to jump down that rabbit hole
<LnL> nix itself could also be smart enough (like the direction of nix upgrade-nix)
<LnL> however something separate is easier to build into a static binary and avoids lots of platform specific details it doesn't really need to know about
hmpffff has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]