package-manager
package-manager copied to clipboard
zeek
A package manager for Zeek
We have some automation that puts together multiple bundles with different sets of packages. Lately this has gotten to be quite slow. It appears that this is because git information...
I am wondering whether it wouldn't make sense to add a subcommand which triggers generation of the package documentation, e.g., similar to [cargo-doc](https://doc.rust-lang.org/cargo/commands/cargo-doc.html). The package manager should already be aware...
While working on zeek/package-template#4 I noticed that multiple concurrent `zkg create` operations can race on update of the default package source. I did not check which other operations can trigger...
One should be able to override a configured `templates` by setting `ZKG_DEFAULT_TEMPLATE`. This seems not to work when also using `--configfile`. Reproducer in `zeekurity/zeek:5.0.2` image: - create a config file...
The machinery currently cloning the template repository breaks if the configured template is in a Git detached HEAD state, e.g., in image `zeekurity/zeek:5.0.2`: ```console # Create valid template repo, but...
It'd be good to handle this more gracefully: https://github.com/zeek/packages/actions/runs/3274626082/jobs/5388405156 Copied for reference: ``` 2022-10-18 15:07:00 DEBUG init Manager version 2.13.0 2022-10-18 15:07:00 DEBUG creating source clone of "zeek" at /home/runner/.zkg/clones/source/zeek...
zkg creates a lot of files which are not cleaned up after installation, e.g., from [a user listing their `/var/lib/zkg`](https://zeekorg.slack.com/archives/CTGDGK6EA/p1665675873375119): ``` 219M clones 72K logs 16K manifest.json 37M scratch 393M...
One can currently override the template used during `zkg create` with `--template `. In order to discover `features` of a template `create`'s documentation suggest using `template info` ```console --features FEATURE...
Power users would like to associate additional metadata with a package installation, for example the user conducting the installation or the time of install. Seems like a generic key-val mechanism...
If an installed packaged `foo/A` `depends` on another package `foo/B` (which would have been installed automatically), one can still execute `zkg remove foo/B` without being notified that one might break...