<abathur>
ah, nice, big sur supports /etc/synthetic.d/
<abathur>
if only they had bothered to support it in catalina so that we don't have to maintain more than twice as much code to take advantage of it...
<gchristensen>
.....
<gchristensen>
:D
<abathur>
:)
<abathur>
*I guess they might prove me wrong--I haven't taken the 10.15.6 update yet, so I suppose it's possible...
disasm has quit [Quit: WeeChat 2.0]
disasm has joined #nix-darwin
eraserhd3 has joined #nix-darwin
eraserhd2 has quit [Ping timeout: 256 seconds]
adelbertc has joined #nix-darwin
<thefloweringash>
LnL: a wip jobset sounds good to me. how do we go about doing that?
<LnL>
thefloweringash: what's easiest for comparison is to rebase against a good trunk eval but I can do that
<LnL>
so only outstanding thing I see is the bootstrap tarball
adelbertc has quit [Quit: Connection closed for inactivity]
<thefloweringash>
ideally that would come from hydra
<thefloweringash>
I find tracking the state of staging/staging-next a bit tricky, but in my test the current state of staging breaks ruby
<thefloweringash>
I could make a PR that forces tapi support on for the bootstrap tools instead of waiting for staging, then hydra could produce appropriate tools pretty promptly
<LnL>
we should have a build for it by now right?
<thefloweringash>
IIUC staging becomes staging-next, and staging-next is merged to master
<thefloweringash>
checking the current state of things, the tapi support is in staging only