[Rpm-maint] [rpm-software-management/rpm] Please add documentation explaining how to use alternate libraries from the test suite (Issue #3200)

[Michal Domonkos]

The tests are run in containers spawned from a local Podman image tagged `rpm`. That image is built from `tests/Dockerfile` (currently only Fedora-based). Therefore, rpm-sequoia is taken from that image, not your host.

This image is made by
1. Building the base image (`rpm/base`) from `tests/Dockerfile` (which itself is based on Fedora)
2. Installing your local rpm build artifacts on top of that image and producing the final `rpm` image

This makes testing your code (rpm-sequoia as a prime example) *against* your local rpm build a bit more complicated at the moment. I plan to make this easier (tracked as #2877), however for now, one (very ugly and hacky) way is to either:

1. Adjust the shipped `tests/Dockerfile` so that it builds and installs sequoia system-wide in it

or

1. Remove the following line from `tests/mktree.oci`:
`$PODMAN build --target base -t $IMAGE/base $ARGS`
2. Build your own `rpm/base` image (e.g. run a container on top of the stock `rpm/base`, then manually build and install rpm-sequoia, then commit the container as the `rpm` image)

Yes, this is super convoluted and not user-friendly at all. I'll try to get #2877 done in the near future.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3200#issuecomment-2214672828
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3200/2214672828 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240708/4fb07565/attachment.html>