Arne Welzel

I'm going to close this PR. I don't have the cycles to see this through. I agree with @catenacyber 's last comment that the script looks like a good place...

> Something strange was going on with https://github.com/zeek/zeek-af_packet-plugin/pull/57. Github says it's merged but somehow the changes didn't make it into master. I had set up the previous PR to be...

Should we do this just in zeekctl? As it is today, changing it here will not actually work for most users.

> I'm not following here. Doing a make install of a classic plugin copies its scripts to lib/zeek/plugins/ Sorry, that was me adding to the confusion because I thought that...

> So perhaps we just need to deprecate the use of SCRIPTS in the spicy_add_analyzer() version from ZeekSpicyAnalyzerSupport.cmake? As discussed yesterday, to me this actually seems a valid approach, too....

> Yeah, in principle people could just use normal CMake installation tools, but the trick is finding the destination path. Providing help with that would be good. Though the next...

> I have a recent clone of all of the package repos and of the 48 packages with a bro-pkg.meta, only 4 of them have a zkg.meta as well. More...

Possibly related: https://github.com/zeek/broker/issues/346

Moved issue to zeekctl. I suppose we could run the following hunk regardless of what `ifconfig` / `ip address` returned and add them to the list: https://github.com/zeek/zeekctl/blob/33ff7b2c328c70bc39320a9baa6a113c2cc6b383/ZeekControl/config.py#L780-L787 Over here: ```...

> A basic question is which ones are available under what compilers/platforms. I think this we should leave up to other documentation and the developer to understand compiler and platform...