Robin Sommer

Iirc these used to go into a scripts directory associated with the plugin, which the plugin would automatically add to ZEEK_PATH so that they would be found. With the the...

> As discussed yesterday, to me this actually seems a valid approach, too. I've [opened a PR](https://github.com/zeek/package-template/pull/34) to remove the rendering from the package-template as that seems confusing/misleading today given...

No strong opinions here (other than that it'll be good to address this!), just a couple of notes: - I'd much prefer a solution that doesn't change Zeek's semantics of...

> One other I'd add (possibly as part of #40) is installing/running the Windows agent as a service instead of just a regular process. Yeah, that applies in some form...

Good thought. I'd say we aren't quite there yet as it will need some more thinking about setup and configuration as well. I'd probably also prioritize some work on Linux-native...

We already have the `%(XX)s` syntax for `user_vars`, seems we could reuse that here as well. In fact why not just extend users vars so that they cover this as...

> add something to label user vars optional, I think we get what we need here. That's essentially what I meant as well. > Personally, I also think it would...

Doing that error message + "here's what to do if you're sure" sounds good to me too. The one other idea I'd have it leaving it to the package author:...

What's the subject of these emails? Is it `master's head updated: ...`? Mind pasting one mail in here?

This is an actual merge commit, not a fast-forward. I was asking because a fast-forward would generate a different kind of a mail ("head updated ..."). And yes, a merge...