Do we also need the same for kqueue and our native resolver ?

@gradinac @normanmaurer We have native-image configuration for Netty MacOS specific nameserver resolution in the graalvm-reachability-metadata
Do we want to move it here?
oracle/graalvm-reachability-metadata#103

@normanmaurer I think you are right, at the very least we would need the resource-config.json for bundling up the native libraries, and probably some additional JNI metadata

@violetagg This is very nice, thank you for listing it here! :) I think it would make sense to move it to Netty itself - in this way, these features will work out of the box with Netty. It may make sense to keep them in the metadata repo for now also so that older versions of Netty can still work properly

Should these 2 be done as part of this or a follow-up PR?

@normanmaurer epoll support for graal native is useful on its own as I dont think people often deploy on macos hosts - and if they do, they can use nio instead of kqueue.

Let me pull in this first. We can do the rest as a followup

@gradinac can you also do a PR for main ?

Sounds good :) I think we won't need the same thing for Netty 5 on main - it shouldn't need the initialize-at-run-time flags though we may need to tweak the metadata - do you by any chance have a Netty 5 example with Epoll that I could test out with native-image?