> We'll want to be able to do stuff like use cmake to compile something against
> rpm in the test-suite (but that's yet another story).
Oh, this is actually a very good point. It's not something I had in mind
previously, but it's yet another reason to just reuse the same Dockerfile image
for both building and testing, indeed :smile: (which is in line with the
planned solution of this ticket).
> Edit: I remember now (after re-reading some of the commentary in this
> ticket): the mktree.fedora case was needed to allow testing the locally built
> binary against that distro version, whereas the CI case is different. That
> was how and why it was so special. I'll just stock on some popcorn and sit
> back to see what happens in this space π
Ack, yes, that's the thing. We want both portability and integration with a
local build for native development.
And yup, popcorn is in order, indeed :laughing:
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2643#issuecomment-1713783267
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2643/1713783...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
