So I found a bug in NetBSD and I'd like to fix it myself, but I'm having trouble with their lack of documentation. I did some more research and asked around and... it seems NetBSD doesn't have any documentation explaining how to compile only a part of the system.
It has documentation explaining how to build the kernel, the entire userland, how to update it from source instead of binaries, and things of the sort, but nowhere does it say how to compile only dkctl or any other command.
Apparently, you're expected to compile the entire thing. Now I have to do this shit on a Pentium 4 because that's where I run NetBSD. Of course, I can cross compile it on a different machine, but that just complicates things further. This comes after I found out the wiki can only be modified by NetBSD developers earlier which prevented me from fixing some typos, grammar, and incorrect information I found.
NetBSD can be quite asinine. This development process wastes a lot of developer time and I'm sure it shies away potential contributors like it's doing here.
There's more nonsense like this in other places of the system too: for instance, NetBSD doesn't have anything like OpenBSD's syspatch, FreeBSD's freebsd-update, or the Linux approach where there's no base system and whatever you'd call a "base" gets updated by the package manager. This means that NetBSD binary releases accumulate unpatched security vulnerabilities that they expect you to fix by compiling the system yourself. This i