Zig, like rust & openjdk can be installed via a binary package or compiled locally. Adding a virtual would avoid doing `|| ( zig... zig-bin... )` which would improve readability & version enforcement. I would make the PR myself but currently we ship zig-bin to more architectures than zig and I do not know what to do here. It will be either keywording zig or unkeyworing the binary variant. I feel like the latter would be better as it is less work for the arch teams. Another thing is the maintainership. I think it would make sense for one person to maintain the three packages. Eric, would you be interested in also maintaining the virtual package?
The keywords on the virtual package only need to be matched by one of the providers. I don't see why you would need to update keywords on either zig or zig-bin.
I did not know this. I'll make a PR then!
