On 8/25/20 1:27 AM, Jan Grashöfer wrote:
I think the underlying issue extends to the pcaps as well. If I am not
mistaken, a significant number of test cases make use of the same pcaps.
Having multiple copies of them scattered across different repositories
doesn't feel right.
Good point, yeah.
On Tue, Aug 25, 2020 at 3:27 AM Jan Grashöfer
wrote:
>
> I like that idea! It would be great to have a standard process for
> generating docs for each package.
>
I've been working[1] on a template for Zeek packages that consist only of
scripts. It's based heavily on the plugin-support[2] in
On 25/08/2020 09:46, Robin Sommer wrote:
Agree, and I'd extend that to packages in general, you be a job for an
extended packages.zeek.org to provide autogen'ed documentation.
I like that idea! It would be great to have a standard process for
generating docs for each package.
On 24/08/2020
On Mon, Aug 24, 2020 at 14:15 -0700, Jon Siwek wrote:
> * What's the LTS policy for packages?
Good question. I think would tie it to the Zeek LTS policy, with a
"blessed" version of the meta-package that we recommend (and maintain)
for each currently maintained Zeek version.
Robin
--
Robin
On Mon, Aug 24, 2020 at 11:49 -0700, Johanna Amann wrote:
> This, from my point of view, it would be neat to have a way to still
> easily install a rather large set of packages (potentially nearly
> everything that is in policy at the moment) and run test on them.
While I agree that
