Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move policy scripts into packages #414

rsmmr opened this issue Jun 14, 2019 · 2 comments


2 participants
Copy link

commented Jun 14, 2019

This idea has been floating around for a while: The non-standard scripts in policy/ might be better maintained as external packages these days. That way they could be updated outside of Zeek releases; and also conceptually, there isn't really that much that makes them that special compared to other packages.

We'd need to make the upgrade path smooth.
We'd probably still recommend a default set of packages to people and could keep shipping a local version of those packages as a default.


This comment has been minimized.

Copy link

commented Jun 15, 2019

Are there more benefits to this besides being able to update them outside the normal Zeek release cycle ?

Was thinking that updates to policy/ scripts haven't been too common or critical at least recently (skimming the git logs, there's only a few changes of much significance since last release). Then also moving Zeek itself into a more frequent release schedule also makes it less an issue.

Can't think of an overall objection to doing this, just benefits seem minor.

As for implementing smoothly: could move them to git submodules so that zkg can install them independently, but then we can have the zeek distribution still include and install them by default unless user configures it not to.

@rsmmr rsmmr added this to the 3.1.0 milestone Jun 17, 2019


This comment has been minimized.

Copy link
Member Author

commented Jun 17, 2019

The plan is to go through policy/ during the next cycles and take stock what makes sense to move.

@jsiwek jsiwek added this to Unassigned / Todo in Release 3.1.0 via automation Jun 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.