zig-build-zlib

Hi Mitchell! I've run into and used a few of your repos where you've put together a build.zig for some other C lib, like here and for pcre2, so first of all - thanks! also libxev looks awesome :) I wonder though, why is this repos directory structure organized like this? I mean, isn't it better to fork the upstream repo and just add a build.zig? I've done that for a bunch of projects and upgrading the base lib is usually just a git rebase away, potentially fixing some issues... and it sort of feels like it's closer to upstreaming that way, no? I see you have multiple repos organized just like this, and this is at least the second where we have overlap (the other is utf8proc, which I have a build.zig for over at https://github.com/actonlang/utf8proc/tree/zig-build). I would very much like to cooperative on these things in the zig community so that perhaps some of these build.zig files might actually be accepted into the upstream repo (I did get zig v0.11 fixes into the pcre2 one, yay!). I'm curious, what's the appeal to this sort of organization? This isn't meant as any critique, if this is what works best for you that's cool too.