On Mon, Aug 31, 2020 at 2:14 AM Robin Sommer <ro...@corelight.com> 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
