condorcore-keyring/Makefile

PREFIX ?= /usr/local
KEYRING_TARGET_DIR=$(DESTDIR)$(PREFIX)/share/pacman/keyrings/
KEYRING_FILES=$(wildcard build/*.gpg) $(wildcard build/*-revoked) $(wildcard build/*-trusted)
SOURCES := $(shell find keyring) $(shell find libkeyringctl -name '*.py' -or -type d) keyringctl

all: build

lint:
	black --check --diff keyringctl libkeyringctl tests
	isort --diff .
	flake8 keyringctl libkeyringctl tests
	mypy --install-types --non-interactive keyringctl libkeyringctl tests

fmt:
	black .
	isort .

check:
	./keyringctl -v check

test:
	coverage run
	coverage xml
	coverage report --fail-under=100.0

build: $(SOURCES)
	./keyringctl -v build

clean:
	rm -rf build

install: build
	install -vDm 755 $(KEYRING_FILES) -t $(KEYRING_TARGET_DIR)

uninstall:
	rm -f $(KEYRING_TARGET_DIR)/archlinux{.gpg,-trusted,-revoked}
	rmdir -p --ignore-fail-on-non-empty $(KEYRING_TARGET_DIR)

.PHONY: all lint fmt check test clean install uninstall
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`PREFIX ?= /usr/local`
			`KEYRING_TARGET_DIR=$(DESTDIR)$(PREFIX)/share/pacman/keyrings/`
feature(keyringctl): use build command to create final artifacts This allows an easy to use cli which invokes the export function to get the keyring and uses the ownertrust and revoke functions to write all artifacts into a target directory. 2021-10-21 14:04:16 -05:00			`KEYRING_FILES=$(wildcard build/.gpg) $(wildcard build/-revoked) $(wildcard build/*-trusted)`
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-26 16:40:11 -06:00			`SOURCES := $(shell find keyring) $(shell find libkeyringctl -name '*.py' -or -type d) keyringctl`
Add Makefile 2012-02-13 07:37:52 -06:00
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`all: build`
Add Makefile 2012-02-13 07:37:52 -06:00
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`lint:`
feature(ci): add testing and coverage data to gitlab ci artifacts 2021-11-01 11:36:02 -06:00			`black --check --diff keyringctl libkeyringctl tests`
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`isort --diff .`
feature(ci): add testing and coverage data to gitlab ci artifacts 2021-11-01 11:36:02 -06:00			`flake8 keyringctl libkeyringctl tests`
			`mypy --install-types --non-interactive keyringctl libkeyringctl tests`
Add Makefile 2012-02-13 07:37:52 -06:00
feature(make): adding `fmt` target to format the project accordingly 2021-10-24 15:10:14 -05:00			`fmt:`
			`black .`
			`isort .`

feature(ci): run keyring integrity check if keyring or code changes 2021-11-07 16:31:19 -06:00			`check:`
			`./keyringctl -v check`

feature(keyringctl): adding basic infrastructure for running tests 2021-10-31 11:53:20 -06:00			`test:`
Makefile: Use coverage instead of pytest Makefile: Run pytest via coverage in `make test` to also generate a coverage report. 2021-10-31 14:26:27 -06:00			`coverage run`
Add more specific coverage configuration pyproject.toml: Set specific source for `toolscoverage.paths` (as we only provide one module). Set `tools.coverage.run.relative_files` to true (although it is still bug riddled and does not seem to work as advertized in regards to xml output: https://github.com/nedbat/coveragepy/issues/963, https://github.com/nedbat/coveragepy/issues/1147). Set `tool.coverage.xml.output`, so we don't have to provide it on the commandline. Makefile: Do not provide an output file to the coverage xml call, as we do that in configuration now. 2021-11-01 15:25:11 -06:00			`coverage xml`
Fail test target under 100% test coverage Makefile: Fail coverage report below 100% test coverage. 2021-11-14 09:10:23 -06:00			`coverage report --fail-under=100.0`
feature(keyringctl): adding basic infrastructure for running tests 2021-10-31 11:53:20 -06:00
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-26 16:40:11 -06:00			`build: $(SOURCES)`
feature(keyringctl): use build command to create final artifacts This allows an easy to use cli which invokes the export function to get the keyring and uses the ownertrust and revoke functions to write all artifacts into a target directory. 2021-10-21 14:04:16 -05:00			`./keyringctl -v build`
Add Makefile 2012-02-13 07:37:52 -06:00
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-26 16:40:11 -06:00			`clean:`
			`rm -rf build`

			`install: build`
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`install -vDm 755 $(KEYRING_FILES) -t $(KEYRING_TARGET_DIR)`
Add Makefile 2012-02-13 07:37:52 -06:00
Makefile: Change to use new targets Makefile: Remove soon unneeded targets for dist and upload. Add lint and build targets. Simplify the installation and uninstallation target. 2021-10-16 17:41:17 -05:00			`uninstall:`
			`rm -f $(KEYRING_TARGET_DIR)/archlinux{.gpg,-trusted,-revoked}`
			`rmdir -p --ignore-fail-on-non-empty $(KEYRING_TARGET_DIR)`
Add Makefile 2012-02-13 07:37:52 -06:00
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-26 16:40:11 -06:00			`.PHONY: all lint fmt check test clean install uninstall`