Jon Siwek

> Generally, I expect the order of precedence to be: > > 1. Command line options I explicitly set, > 2. Environment variables, > 3. Local config file, > 4....

> * New `zkg autoconfig` runs store the location of `zeek-config` in its config file > * `zkg` passes this value as `ZKG_ZEEK_CONFIG` into the environment of the `build_command` >...

> what if there is no configuration at all? In this case, running `zkg install` will report that it installed correctly, but from what I can tell, it will only...

Yes, seems like a fairly unintuitive pitfall: 1. the default plugin skeleton/CMake creates the symlink `./build/scripts` 2. the obvious thing for bro-pkg users is to set `plugin_dir` to `./build/` 3....

> That makes sense. How would you feel about a more strong recommendation to use .tgz files for plugin packages [here](https://docs.zeek.org/projects/package-manager/en/stable/package.html#plugin-dir-field)? Sure, do you have a particular suggestion for language/formatting...

> For distributing scripts then I'd go back to my initial solution - what do you think about modifying the `state_dir` default to `$prefix/bro/lib/bro-pkg` or similar instead of the user's...

Thanks, seems like a neat idea to me, too, and I'd also try to make what's happening clearer to user. An alternate way to do that may even be to...

A simple alternative/workaround at the moment should be something like `bro-pkg bundle my.bundle && bro-pkg unbundle my.bundle`

> BTW, what project do you build? Not a public one if you were hoping for exact way to repro, but let me know if you can't and want me...

The build from #3077 does fix my issue, thanks.