Closed EWickens closed 3 years ago
Hey, thanks for the feedback! Which version of Zeek are you using? The current master was updated to be compatible with the changes of the upcoming Zeek release.
No problem. My apologies I should have included that - my Zeek version is set as 3.2.3 based to match a dockerfile contained within ActiveCM's single-system Zeek cluster project. Cheers!
Hmm... so there are breaking changes with Zeek 4.0. It would be possible to add a compatibility layer to support versions down to 3.1. However, your approach to use the latest release (2.1.2) of the plugin is totally fine. Furthermore, the package manager should use the latest release by default. I am tempted to make a major release of the plugin once Zeek 4.0 is available to indicate the breaking changes and omit the compatibility layer. Would that work for you?
That would be totally fine. I'm relatively new to using your plugin but will be using it going forward so I'm happy to keep using 2.1.2, just wanted to raise this with you for visibility :)
Thanks for the great work!
Cool, in that case I will stick to the plan of doing a new release for Zeek 4.0. Thanks a lot for bringing this up. I will keep the issue open until then.
Hey,
Have been building this within a docker container on the latest release (c993fc275864fd068e6a816fd2f3892a0d5f4cb7)
Encountered an issue during compilation which I've provided below, I rolled back to the 2.1.2 release and all is working on install again.
Hope this helps!