Since I already started describing the new architecture, here's a perhaps
simpler outline of how it works now (`mktree` is wired into the `make`):
1) `mktree build`
* builds a base OS tree
* builds RPM natively and make installs it into the base OS tree
2) `mktree check`
* runs `rpmtests` in a container (on top of the OS tree), e.g. with bwrap or
podman (depending on the backend used)
* test1
* `run rpm ...` (runs "natively" in the container, shouldn't make
destructive changes)
* test2
* `runroot rpm ...` (runs in a per-test bwrap container, this enables
destructive changes)
* `ls $RPMTEST`
* ...
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2559#issuecomment-1632406555
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2559/c1632406...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
