Closed ckreibich closed 2 years ago
Thanks a lot Christian! I missed testing the plugin while loading packages. I reproduced the problem, merged your changes (fixing a small typo in zkg.meta: scripts
--> script_dir
) and created a new release.
That was super fast, thank you Jan! :raised_hands:
When you install versions of the package >= 3.0, running Zeek with the installed package throws a bunch of warnings:
It does actually run, but that's just luck — with more severe script-level clashes it'd bail out. The problem is that the package has an unintentional double-use of the scripts folder: the plugin machinery automatically picks it as its location of Zeek scripts required for the plugin to function, and
zkg
's packaging also picks it up via the explicit instruction inzkg.meta
.This PR simply moves the package-level stuff to a subdirectory, as a placeholder. That placeholder still avoids the warning that e3aea14a84c505367cd6277c67b6def2f5ea9d5f wanted to fix.