On Mon, Aug 24, 2020 at 6:43 AM Robin Sommer wrote:
> 1. Move each into a a separate repository on the zeek/ GitHub
>account.
>
> 2. Similar, but to avoid cluttering zeek/, create a new GitHub
>organization "zeek-packages".
I'm thinking (2). Technically, either one can
On 8/24/20 11:49 AM, Johanna Amann via zeek-dev wrote:
* Testing:
Currently, some of the policy scripts have tests that use Zeek
functionality in rather unique ways / or are the only tests for some
Zeek functionality. The SSL validation scripts are one example.
This, from my point
On 8/24/20 9:51 AM, Robin Sommer wrote:
Also, one additional thought: Jon reminded me that zkg can manage
dependencies already. So the "collection" I mentioned could be a
meta-package that depends on all the ones we want.
Yeah, agreed -- I prefer #2 for the same reason.
Best,
Christian
Hi,
just a few thoughts about this. Generally - I like the idea of breaking this up.
I would like to list a few thoughts about additional technical points that
we should perhaps think about and that play into this decision.
* Testing:
Currently, some of the policy scripts have tests that use
On Mon, Aug 24, 2020 at 11:26 -0500, Michael Dopheide wrote:
> I like (2) for cleanliness.
Vote counted!
> there should be an easy way to distinguish them from other packages
> when doing a 'zkg list'.
Good point.
Also, one additional thought: Jon reminded me that zkg can manage
I like (2) for cleanliness.
I think some people would be fine with one large package, but in other
cases, you may want the ability to easily enable/disable various standard
scripts. Probably not wanting to maintain the same script in
multiple places, I think that eliminates (3). Towards, (4) &
Looking for some thoughts here. One of the items on the roadmap for
4.0 is moving scripts that currently live in policy/ over into Zeek
packages. The goals here are to (1) facilitate maintaining & testing
them independently of Zeek releases; and (2) come to a more flexible
notion of "default
