Arne Welzel

> There's a question here about how to handle built-in plugins against external plugins. If an external plugin is loaded when one with a plugin with the same name is...

> However, it'd be really handy to provide something like --favor-builtin-plugins and/or --favor-dynamic-plugins (possibly with per-plugin choices?). I'm a bit unclear if that's worth it and who the users are...

> Yeah, sounds good Arne. I agree that it's progress. Mostly just better messaging and avoid to crash. > If such Zeek's would include the package metadata out of the...

Likely related: https://community.zeek.org/t/logging-issue-after-upgrade-to-lts-5-0-0/6613/4

I had chatted with @rsmmr about this and he could also see shipping the plugin's code within the Zeek source. I'm leaning towards preferring that too, but building it in...

> Given that there are some todos, likely to be addressed in this process (e.g., https://github.com/J-Gras/zeek-af_packet-plugin/issues/29), See my last commit - I think using just the latest is fine for...

This PR is currently pointing at a branch in Jan's repo where the kernel-headers dependency has been removed and seems that all distros we have in `ci/` are happy with...

> The main argument I'm aware of for going the submodule route is that resulting improvements to the plugin become available also to users who pull in the plugin via...

> The main argument I'm aware of for going the submodule route is that resulting improvements to the plugin become available also to users who pull in the plugin via...

> Also, wouldn't problems like #2403 also come up if it's included directly, not via a submodule? We'd still be building a plugin. Yes. Technically the problem will continue to...