package-manager
package-manager copied to clipboard
zeek
A package manager for Zeek
`zkg` generally does not clean up after itself when it puts stuff in its `scratch` directory. For users going through a lot of packages this can add up (since `zkg`...
This PR contains a number of cleanups of the project. - Move most project config from `setup.py` to `pyproject.toml`: with this one can use modern tools like e.g., rye or...
When zkq was running tests for each version, if a version failed, it was printing an error without context of the test dir and clone dir, and continuing. It looks...
When a package's test cases fail, `zkg` produces `zkg.test_command.stdout` and `zkg.test_command.stderr` files in the package's clone in `zkg`'s scratch space — but the user never learns about that, not even...
When doing `zkg install`, a [check is made](https://github.com/zeek/package-manager/blob/5ade27d716fd65342be592abf277eea114fefaa7/zkg#L382-L384) to ensure the local repository isn't dirty. If it is, the install fails. For development purposes, it would be convenient to have...
On machines with locked-down network connectivity `zkg`'s tendency to clone or fetch repos isn't helpful, and often not required. It'd be nice to tell it to work without remote connectivity....
With zeek/spicy-ldap moving into Zeek with zeek-6.1.0 the package cannot be installed on >=zeek-6.1.0 anymore. We usually document this in the package README, but it would be great if we...
`zkg` still supports various Bro-era environment variables, `.bro` files, `bro-config` invocations, etc that we should remove at this point. (This'll be a reason to jump to 3.0., so a good...
We keep seeing that people run `zkg autoconfig` on the standard Zeek-bundled `zkg` setup. Permission issues aside this is at least confusing and at worst introduces brittleness because the config...
The test failed after a merge to master, but a re-run fixed it.. This is for record keeping in case it happens again. https://cirrus-ci.com/task/4539628506578944?logs=test#L1 ``` ci/test.sh [#2] tests.install-on-tty ... failed...
