[Zeek-Dev] Re: Moving policy scripts into packages
On Mon, Aug 31, 2020 at 2:14 AM Robin Sommer wrote: > - zkg: > - Distinguish standard/recommended packages from others. Not sure what's meant there, but names/listings would all use `zeek/zeek-packages/` as a prefix and be a way of distinguishing. If it's more about organizing meta-packages to have a secondary-level of optional/recommended content, there's maybe already a `suggests` metadata field that helps: https://docs.zeek.org/projects/package-manager/en/stable/package.html#suggests-field > - Could we add a way to "prime" zkg's package cache so that a Zeek > distribution could distribute a snapshot of "zeek-packages" for > direct use; but zkg would still pull in updates if online access > is available? It's possible. Needs more planning in terms of what's desired/required for the distribution and integration with CMake build/install logic. * Will `zkg` now be a required dependency for installing `zeek` ? * In any case, might assume CMake install logic can at least use `zkg` if available. Then, it may be convenient if the package distribution format is already something `zkg` knows well. Say, a "bundle". * After a `zkg unbundle`, packages should be set up to track the real/online git repo URLs such that `zkg refresh && zkg upgrade` could be used to receive updates. * In the case `zkg` isn't required/available when installing `zeek`, I'm sure there's some duplication/re-implementation of install logic we could add in the `zeek` CMake logic to install packages into usable locations, but it may generally be tricky/fragile to allow `zkg` to take over such an installation "after the fact". If there were such a change of mind in the person doing an install, it might be easiest to "do the `zeek` install process again, this time with `zkg` available". - Jon ___ zeek-dev mailing list -- zeek-dev@lists.zeek.org To unsubscribe send an email to zeek-dev-le...@lists.zeek.org
[Zeek-Dev] Re: Moving policy scripts into packages
Great summary, thanks Robin. On 8/31/20 2:14 AM, Robin Sommer wrote: - zkg: - Could we add a way to "prime" zkg's package cache so that a Zeek distribution could distribute a snapshot of "zeek-packages" for direct use; but zkg would still pull in updates if online access is available? Related to this, I was wondering about zkg's status as an affiliated project ... if we strengthen the notion of packages from the core distribution, we may want to ensure zkg can be available from the outset (as a core component)? I tried to look at some equivalents in other environments ... for example, it looks like when you install Python/Ruby from the official tarballs you get pip/gem out of the box. Best, Christian ___ zeek-dev mailing list -- zeek-dev@lists.zeek.org To unsubscribe send an email to zeek-dev-le...@lists.zeek.org
[Zeek-Dev] Re: Moving policy scripts into packages
To summarize this a bit, below is what I think what I heard so far. Feel free to respond further, I'll move this over into the ticket later once we have consensus. Robin - General preference to keep packages in individual repositories hosted inside a new GitHub organization "zeek-packages". - Management through a meta-package that lists lists all desired packages as dependencies. The meta-package can version content by pinning packages to blessed versions. - Tie these meta-packages to the current Zeek releases. To take this a bit further: - I imagine this means that we'll have three meta-packages at any point of time: "zeek-packages-current", "zeek-packages-lts", and "zeek-package-devel". When a new release comes out, these rotate through. - People can install packages for older (now unsupported) Zeek versions by picking a older version of the corresponding meta-package. - The Zeek distribution can either download the current version of the meta package on install; or even just include the full content somehow (also see "zkg" below). - Testing - Need to make tests standalone and less dependent on Zeek versions. - Should make standard btest infrastructure available to tests (e.g., Zeek's btest helpers, pcaps). - Provide integration tests that execute across the full set of "zeek-packages". - Development - Make it it easy to work multiple packages at once (e.g., to update baseline; get all dependencies in place) - Documentation - Use Zeekygen to document the full content of a meta package at once; can host either on docs.zeek.org or packages.zeek.org. - Make it easy to autogen docs for individual packages (ideas: GitHub Pages through Vlad's cookie-cutter; autogen on packages.zeek.org) - zkg: - Distinguish standard/recommended packages from others. - Could we add a way to "prime" zkg's package cache so that a Zeek distribution could distribute a snapshot of "zeek-packages" for direct use; but zkg would still pull in updates if online access is available? ___ zeek-dev mailing list -- zeek-dev@lists.zeek.org To unsubscribe send an email to zeek-dev-le...@lists.zeek.org
