| 18 Oct 2025 |
 Alyssa Ross | if there isn't urgency, the thing to do is finish fixing valgrind | 12:33:24 |
 dramforever | you seem very vehemently against the idea of nixpkgs just not disabling valgrind for mesa on musl+llvm | 12:33:56 |
 matthewcroughan | No, I just think it's probably the right thing to do, like who needs valgrind on mesa? | 12:34:25 |
| dramforever | this is the "urgency" i've been talking about, you've been urging this for like twenty minutes | 12:34:31 |
| matthewcroughan | Like, it's for development and debugging, no? | 12:34:37 |
| matthewcroughan | and it increases the closure size quite a bit probably anyway | 12:34:54 |
| matthewcroughan | Ah yeah it also depends on perl | 12:35:33 |
| matthewcroughan | So can't have a perlless system with this in :D | 12:35:46 |
| dramforever | it is for development and debugging, which a lot of nixpkgs users do | 12:35:50 |
| Alyssa Ross | if you want to argue for disabling valgrind by default on mesa, that's very different from arguing for doing it on "some platforms". | 12:36:25 |
| Alyssa Ross | but presumably at some point somebody decided that Valgrind should be included in Mesa, so it's not necessarily going to be easy to find consensus for | 12:37:26 |
| matthewcroughan | It's optional via override so it's fine | 12:37:46 |
| matthewcroughan | Like I think if it's optional via override, then it doesn't need to touch nixpkgs | 12:38:23 |
| matthewcroughan | And if it's not optional via override like this is, then that's the thing that needs to change. But things should also compile with musl without override, which in this case would require fixing valgrind upstream | 12:39:12 |
| Alyssa Ross | again, mesa works fine with musl | 12:39:26 |
