| 18 Oct 2025 |
Alyssa Ross | and then your fork fades away | 12:30:51 |
dramforever | yeah just do that | 12:30:54 |
Alyssa Ross | that's what happened with my own musl work | 12:30:55 |
Alyssa Ross | now everything works in upstream Nixpkgs and I no longer have a fork | 12:31:04 |
Alyssa Ross | but you can't get there overnight | 12:31:06 |
dramforever | if you don't make your work block on having nixpkgs merge stuff what's the urgency | 12:31:45 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | There isn't? I'm just firing off PRs as soon as I find them | 12:32:23 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Like i'm not letting things hang around | 12:32:43 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | * Like i'm not letting things hang around unsubmitted | 12:32:51 |
Alyssa Ross | you were asking about mesa/valgrind in a way that suggested urgency | 12:33:09 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Maybe I'm just excited? :D | 12:33:19 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Not urgent at all | 12:33:23 |
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 @ 39c3 (DECT 94667 or 97340 or 67192) | 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 @ 39c3 (DECT 94667 or 97340 or 67192) | Like, it's for development and debugging, no? | 12:34:37 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | and it increases the closure size quite a bit probably anyway | 12:34:54 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Ah yeah it also depends on perl | 12:35:33 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | 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 @ 39c3 (DECT 94667 or 97340 or 67192) | It's optional via override so it's fine | 12:37:46 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Like I think if it's optional via override, then it doesn't need to touch nixpkgs | 12:38:23 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | 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 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | s/musl/llvm/g | 12:39:40 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | I just woke up :D | 12:39:50 |
matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Crawled to my computer and started building | 12:40:02 |