2022-12-02 11:03:50 -05:00
|
|
|
prefix ?= /usr
|
|
|
|
|
|
2024-06-06 07:48:47 -04:00
|
|
|
SOURCE_DATE_EPOCH ?= $(shell git log -1 --pretty=%ct)
|
|
|
|
|
# https://reproducible-builds.org/docs/archives/
|
|
|
|
|
TAR_REPRODUCIBLE = tar --mtime="@${SOURCE_DATE_EPOCH}" --sort=name --owner=0 --group=0 --numeric-owner --pax-option=exthdr.name=%d/PaxHeaders/%f,delete=atime,delete=ctime
|
|
|
|
|
|
2022-12-02 11:03:50 -05:00
|
|
|
all:
|
|
|
|
|
cargo build --release
|
|
|
|
|
|
|
|
|
|
install:
|
2023-10-12 15:29:31 -04:00
|
|
|
install -D -m 0755 -t $(DESTDIR)$(prefix)/bin target/release/bootc
|
2024-07-16 15:05:02 -04:00
|
|
|
install -d -m 0755 $(DESTDIR)$(prefix)/lib/bootc-experimental/bound-images.d
|
|
|
|
|
install -d -m 0755 $(DESTDIR)$(prefix)/lib/bootc/kargs.d
|
2024-03-19 08:59:52 -04:00
|
|
|
install -d -m 0755 $(DESTDIR)$(prefix)/lib/systemd/system-generators/
|
|
|
|
|
ln -f $(DESTDIR)$(prefix)/bin/bootc $(DESTDIR)$(prefix)/lib/systemd/system-generators/bootc-systemd-generator
|
2023-10-14 17:51:42 -04:00
|
|
|
install -d $(DESTDIR)$(prefix)/lib/bootc/install
|
2023-11-03 16:06:57 -04:00
|
|
|
# Support installing pre-generated man pages shipped in source tarball, to avoid
|
2024-01-17 16:23:42 -05:00
|
|
|
# a dependency on pandoc downstream. But in local builds these end up in target/man,
|
|
|
|
|
# so we honor that too.
|
|
|
|
|
for d in man target/man; do \
|
|
|
|
|
if test -d $$d; then \
|
|
|
|
|
install -D -m 0644 -t $(DESTDIR)$(prefix)/share/man/man5 $$d/*.5; \
|
|
|
|
|
install -D -m 0644 -t $(DESTDIR)$(prefix)/share/man/man8 $$d/*.8; \
|
|
|
|
|
fi; \
|
|
|
|
|
done
|
2023-11-03 16:06:57 -04:00
|
|
|
install -D -m 0644 -t $(DESTDIR)/$(prefix)/lib/systemd/system systemd/*.service systemd/*.timer
|
|
|
|
|
|
2024-05-31 16:01:41 -04:00
|
|
|
install-with-tests: install
|
|
|
|
|
install -D -m 0755 target/release/tests-integration $(DESTDIR)$(prefix)/bin/bootc-integration-tests
|
|
|
|
|
|
2022-12-02 11:03:50 -05:00
|
|
|
bin-archive: all
|
2024-06-06 07:48:47 -04:00
|
|
|
$(MAKE) install DESTDIR=tmp-install && $(TAR_REPRODUCIBLE) --zstd -C tmp-install -cf target/bootc.tar.zst . && rm tmp-install -rf
|
2022-12-02 11:03:50 -05:00
|
|
|
|
2024-05-31 16:01:41 -04:00
|
|
|
test-bin-archive: all
|
2024-06-06 07:48:47 -04:00
|
|
|
$(MAKE) install-with-tests DESTDIR=tmp-install && $(TAR_REPRODUCIBLE) --zstd -C tmp-install -cf target/bootc.tar.zst . && rm tmp-install -rf
|
2023-02-04 15:55:14 -05:00
|
|
|
|
2024-06-10 14:07:11 -04:00
|
|
|
test-tmt:
|
|
|
|
|
cargo xtask test-tmt
|
2023-01-18 17:39:03 -05:00
|
|
|
|
2024-07-15 17:44:59 -04:00
|
|
|
# Checks extra rust things (formatting and select clippy lints)
|
|
|
|
|
validate-rust:
|
|
|
|
|
cargo fmt -- --check -l
|
|
|
|
|
cargo clippy -- -D clippy::correctness -D clippy::suspicious
|
|
|
|
|
.PHONY: validate-rust
|
|
|
|
|
|
|
|
|
|
validate: validate-rust
|
tests: Add pytest and nushell based tests
I've been trying to keep this project in "one" programming
language by writing even tests in Rust...but specifically
for our integration tests it's pretty painful not just to
compile them but have to deal with baking them into the base image.
The tmt framework is very GHA like in that it scrapes the
git source tree and copies it into the target environment, which
works really well with scripts.
Now, if you know me you know I am not a fan of dynamic programming
languages like bash and Python. I'm one of those folks that actually
tries to use Rust for things that feel like "scripts" i.e. they're
*mostly* about forking external processes (see the xtask/
crate which uses "xshell").
Some of our testing code is in Rust too. However...there's a giant
tension here because:
- Iteration speed is very important for tests and scripts
- The artifact being an architecture-dependent binary pushes us
to inject it into container images; having the binary part
of the bootc image under test conceptually forces us to reprovision
for each test change, which is super expensive
Most other people when faced with the testing challenge would
just write shell scripts (or Python); that's definitely what tmt
expects people to do.
The podman project has a mix of a "bats" suite which is all
bash based, and a Go-based framework.
The thing is: bash is easy to mess up and has very little ability
to do static analysis. Go (and Python) are very verbose for forking external
processes.
I've been using https://www.nushell.sh/ for my interactive shell
for quite a while; I know just enough to get by day to day
(but honestly sometimes I still type "bash" and run a few things there
that I know how to express in bash but not nu)
Anyways though, nushell has a lot of desirable properties for
tests (which are basically scripts):
- Architecture independent
- Running an external process requires zero ceremony; it's the
default!
- But it *is* easy to e.g. scrape JSON from an external binary
into a rich data structure
- A decently rich standard library
The downside is, it's a new language. And in the end, I'm
not going to say it's the only way to write tests...maybe we
do end up with some more bash. It wouldn't be the end of the world.
But...after playing with this, I definitely like the result.
OK, and after some debate we decided to add Python too, so this
demos a pytest test.
Signed-off-by: Colin Walters <walters@verbum.org>
2024-06-22 09:18:49 -04:00
|
|
|
ruff check
|
2023-11-01 14:56:53 +01:00
|
|
|
.PHONY: validate
|
|
|
|
|
|
2023-01-18 17:39:03 -05:00
|
|
|
vendor:
|
|
|
|
|
cargo xtask $@
|
|
|
|
|
.PHONY: vendor
|
|
|
|
|
|
|
|
|
|
package-rpm:
|
|
|
|
|
cargo xtask $@
|
|
|
|
|
.PHONY: package-rpm
|