<copumpkin>
sometimes I rebuild the stdenv on my old MBP 13"
<copumpkin>
and I'm blown away at how slow it is
<copumpkin>
several hours
<copumpkin>
and then I'm astounded that I did any of the pure darwin stdenv back in the day when I didn't know better and had 3 LLVM+clang rebuilds per bootstrap and each of them took this long
<copumpkin>
on this laptop
<copumpkin>
current me is impatient enough that I'd probably have thrown the laptop out the window by now :)
carlosdagos has joined #nix-darwin
hamishmack has quit [Ping timeout: 244 seconds]
hamishmack has joined #nix-darwin
matthewbauer has joined #nix-darwin
trcc has joined #nix-darwin
matthewbauer has quit [Ping timeout: 250 seconds]
philr has quit [Quit: WeeChat 2.2]
trcc has quit [Remote host closed the connection]
trcc has joined #nix-darwin
<Enzime>
copumpkin: LnL: where does apple-sdk/frameworks.nix come from
<Enzime>
and does it miss dependencies?
<LnL>
no idea actually
carlosdagos has quit [Quit: Connection closed for inactivity]
<LnL>
and /Library/Developer/CommandLineTools is on an unmounted volume
<copumpkin>
nice :)
trcc has quit [Remote host closed the connection]
<nikivi>
what are your guy's thoughts on my universal nix installer idea I posted on #nixos
<nikivi>
would you use this?
trcc has joined #nix-darwin
<copumpkin>
not clear to me how it would work
<copumpkin>
the reason we have so many tools is that they all work quite differently
<copumpkin>
depending on how the underlying language ecosystems and build ecosystems work
<nikivi>
it's just I want to use nix for everything
<nikivi>
but its a struggle
<copumpkin>
some of them use heavily vendored dependencies, others have strong versioning
<copumpkin>
sure, I just mean I get the desire
<copumpkin>
I just have no idea how it would work
<nikivi>
mostly because I have this alias: nix-env -q | fzf | xargs -I{} nix-env -e {}
trcc has quit [Ping timeout: 246 seconds]
<nikivi>
which lets me fuzzy searched through all packages I installed with nix
<nikivi>
and on return, uninstalls it
<nikivi>
> I just have no idea how it would work
<{^_^}>
undefined variable 'I' at (string):195:1
<nikivi>
using the automatic 2nix tools
<nikivi>
or they are not deterministic
<copumpkin>
not always
<copumpkin>
and the tools all work in slightly different ways
<copumpkin>
sometimes they could be more standardized, but in many ways we're constrained by the underlying package ecosystems
<cransom>
part of the issue of 'one X for Y' is that there soooo many Ys. each go/python/nodejs ecosystem has multiple ways to distribute software, and rarely does every package stick to the exact same format.
<nikivi>
well this universal tool doesn't have to be magical
<nikivi>
it can work on some cases
<nikivi>
and on cases it can't it, it tells the user
<nikivi>
it's just odd to have some go packages on nixpkgs
<nikivi>
and others not
<copumpkin>
that's mostly because it took work to put them there
<nikivi>
but it seems nearly all Haskell packages are nix intaallable
<cransom>
frequently i find that if something isn't in nix and i start to bundle it, i find out quickly why it's not already bundled as it's using quirky dependencies or has other undesirable behavior that makes it a huge chore to incorporate for little gain
<copumpkin>
that's because someone put in the work to automate the full package universe
<copumpkin>
and also in part because of differences in the two language ecosystems
<copumpkin>
haskell has hackage, a central place where most haskell packages go
<copumpkin>
there are a few packages not on hackage that we package but you can't auto-discover them
<copumpkin>
go is kind of decentralized
<copumpkin>
mostly uses github as a naming source, and there's no central package manager for it
<nikivi>
so what is your approach to using non nix installable tools
<nikivi>
you install the tool, then edit your configuration.nix to add the package there?
trcc has joined #nix-darwin
trcc has quit []
hamishmack has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]