condorcore-keyring/libkeyringctl
Levente Polyak d0ea790c6a
fix(make): use proper dependency tracking for the build output
Declare the whole keyring data as well as the code as input dependency
for the build target. This way we can properly depend on the build
target for installation without forcing rebuilding on every invocation.

A rebuild will be triggered if either the keyring or the source code
creating the build output changes.

The directories are added to the source dependencies on purpose to
guarantee that changes like deleted files will result in a rebuild.

The mtime of the build directory is force updated on every run to allow
make to track the output artifacts mtime compared against the
dependencies.
2021-11-30 22:54:17 +01:00
..
__init__.py chore(keyringctl): modularize the code for overview and testing 2021-11-30 22:54:12 +01:00
ci.py feature(keyringctl): rework ci module to execute full lint for new certs 2021-11-30 22:54:16 +01:00
cli.py feature(keyringctl): add option to filter listing by trust 2021-11-30 22:54:17 +01:00
git.py feature(keyringctl): rework ci module to execute full lint for new certs 2021-11-30 22:54:16 +01:00
keyring.py fix(make): use proper dependency tracking for the build output 2021-11-30 22:54:17 +01:00
sequoia.py feature(keyringctl): split direct key packets into own directory 2021-11-30 22:54:16 +01:00
trust.py feature(keyringctl): add option to filter listing by trust 2021-11-30 22:54:17 +01:00
types.py feature(keyringctl): add option to filter listing by trust 2021-11-30 22:54:17 +01:00
util.py fix(keyringctl): avoid simplified uid collisions using a hash 2021-11-30 22:54:17 +01:00
verify.py fix(keyringctl): avoid simplified uid collisions using a hash 2021-11-30 22:54:17 +01:00