| 8 Oct 2024 |
 emily | indeed | 18:42:05 |
| emily | in this case, it's not so much a feature as a vital refactor | 18:42:18 |
| emily | Darwin support desperately needs it to be viable; we rushed the 12.3 SDK as an interim measure and we've already had major packages (QEMU, Qt) be unable to be updated without it | 18:42:41 |
| emily | those two projects don't support 12 officially, so we could easily end up in trouble within 6 months even doing security updates | 18:43:19 |
| emily | it's also going to be painful to do backports across different macOS SDK patterns, so landing it early next cycle would be really bad for 24.11 in general | 18:43:47 |
| emily | I think everyone would have preferred this to be happening a month ago but you know how things go | 18:44:02 |
 Randy Eckenrode | Two months to develop and land is about what I expected. I wish I had been able to start this sooner, but it took some time to get the cctools and ld64 updates landed. | 19:43:20 |
| Randy Eckenrode | While I lost some time due to poor Git hygiene and cleaning up my branch, I don’t think it would have made the current cycle regardless. | 19:44:03 |
| Randy Eckenrode | https://gist.github.com/reckenrode/58933e82c687d8026fe19630c0ed699f | 19:44:33 |
| Randy Eckenrode | That’s the flake I used for testing, which took half a week to build. I feel pretty about what kind of breakage to expect. | 19:45:12 |
| Randy Eckenrode | If you just take framework packages, you are fine in most cases. If you use autotools, you may need help linking libiconv because you forgot to do that in `Makefile.am`. If you care about framework internals, you need updated to know about `$SDKROOT`. | 19:46:42 |
| Randy Eckenrode | * If you just take framework packages, you are fine in most cases. If you use autotools, you may need help linking libiconv because you forgot to do that in Makefile.am. If you care about framework internals, you need updated to know about $SDKROOT. | 19:47:14 |
| Randy Eckenrode | (I also lost a ~week to fixing Swift because that is an ugly and slow build process.) | 19:48:10 |
| Randy Eckenrode | And yes, my availability after the 18th unlikely. My wife is scheduled for induction that evening. It could get pushed back a few weeks, but we don’t know yet (but assume not). After that, I’ll probably not have time beyond maybe checking Matrix while taking care of the baby. | 19:50:01 |
| Randy Eckenrode | * And yes, my availability after the 18th is unlikely. My wife is scheduled for induction that evening. It could get pushed back a few weeks, but we don’t know yet (but assume not). After that, I’ll probably not have time beyond maybe checking Matrix while taking care of the baby. | 19:50:13 |
| emily | please don't check Matrix too often :) | 20:09:09 |
| emily | I promise to do my best to solve any issues that come up that aren't far beyond my pay grade. | 20:09:24 |
 vcunat | That formulation feel weird when you don't actually get paid for it :-D | 20:30:13 |
| emily | wait, you haven't been receiving my invoices? | 20:31:31 |
| emily | that explains a few things | 20:31:33 |
| 9 Oct 2024 |
 hexa | soon I'll start contributing and then people on matrix will respect me | 20:47:27 |
| hexa | no payment required | 20:47:31 |
| hexa | * soon I'll start contributing and then people on matrix will respect me | 20:47:38 |
| 10 Oct 2024 |
 SigmaSquadron | I'm still puzzled as to why they said these things about you. The few interactions I've had with you on the infra channel have been nothing but positive! | 00:03:29 |
| hexa | the person on the off-topic room? | 01:49:43 |
| hexa | they failed to map my nickname to my github account 🙂 | 01:50:02 |
 Tristan Ross | The Hyprland thing from earlier today? | 01:50:22 |
| hexa | yeah | 01:50:27 |
| Tristan Ross | I don't really understand what happened since I was just waking up lol | 01:51:54 |
| SigmaSquadron | In reply to @hexa:lossy.network
the person on the off-topic room? yeah there was also another one in the dev room a while back; don't remember the nick | 01:57:30 |
