| 20 Dec 2024 |
 Tristan Ross | A lot of things would require patches to work but at least having a toolchain would be possible | 20:18:03 |
| Tristan Ross | I don't expect a whole lot to work | 20:18:48 |
 K900 | If you want to burn cycles on silly targets that LLVM supports just because LLVM supports them, do MSVC | 20:19:10 |
| K900 | At least that might actually be useful in like five years | 20:19:19 |
| 21 Dec 2024 |
|  @stablejoy:matrix.org left the room. | 05:08:19 |
|  @dmiskovic:matrix.org left the room. | 05:14:00 |
| @stablejoy:matrix.org joined the room. | 06:43:25 |
| K900 | I think I brought this up before, but should we enable build-ids for everything | 07:36:51 |
 p14 | In reply to @k900:0upti.me
I think I brought this up before, but should we enable build-ids for everything Rationale? What are build-ids a function of and does it affect reproducible builds? (Presumably they don't, but would love to understand more what's going on and what they enable). | 11:03:43 |
| K900 | build-ids are basically a hash of the file | 11:11:21 |
| K900 | They're used for debug info matching | 11:11:28 |
| p14 | I see. Is there a pool of debug info somewhere I can easily utilise? | 11:12:08 |
| K900 | We don't build debug info for everything | 11:12:44 |
| K900 | But many things have it cached | 11:12:48 |
| K900 | You can use nixseparatedebuginfod | 11:12:52 |
| p14 | That's pretty cool; I'm wondering how does it connect thing being debugged to the derivation containing the separate debug info. Thinking aloud, presumably it does something like nix-store --query --deriver <path> and then look inside the derivation for the output named 'debug'. | 11:16:29 |
|  Dimitar joined the room. | 19:45:27 |
 Philip Taron (UTC-8) | I'd like to post this | 21:45:12 |
| Tristan Ross | In reply to @philiptaron:matrix.org
I'd like to post this On Discourse? | 21:47:20 |
| Philip Taron (UTC-8) | Yessir. | 21:47:27 |
| Tristan Ross | In reply to @philiptaron:matrix.org
Yessir. Sounds good | 21:48:30 |
| Tristan Ross | I'm thinking we can do a meeting sometime after the new year so we can figure things out for what the SC wants. | 21:50:31 |
| Philip Taron (UTC-8) | The sad (but also great) fact of the matter is that I'm most available over the next couple weeks, since I'm off of work. | 21:57:53 |
| Philip Taron (UTC-8) | Posted: https://discourse.nixos.org/t/community-team-updates/56458/11?u=philiptaron | 21:58:56 |
| Tristan Ross | Oh | 22:02:36 |
| Tristan Ross | Yeah, I'm available on Tuesday to Thursday this week | 22:03:56 |
| Tristan Ross | In reply to @philiptaron:matrix.org
Posted: https://discourse.nixos.org/t/community-team-updates/56458/11?u=philiptaron I thought you were meaning a different discourse post lol | 22:04:12 |
| Philip Taron (UTC-8) | 😬 | 22:04:42 |
| Tristan Ross | It's fine lol | 22:07:04 |
| Philip Taron (UTC-8) | I kept "who authored this" in there, so that if there's "hell no we aren't doing that" it would be clear where the stones ought to be thrown. Don't expect that, though. | 22:08:11 |
