Sorry for the holdup folks, I've been mulling over this quite a bit. The tests
that is.
The test-suite is a deal-breaker really. Rpm's test-suite is the autotest-based
thing, and everything in rpm needs to use that for tests. We can't have
individual bits and pieces bring in their own infra, dependencies and own make
targets for integration.
There are various possible paths here. One is adjusting the tests to use rpm's
test-suite, but I sense there's a strong desire to have the tests runnable
outside rpm. Which is perfectly understandable as the rest of the rpm tests are
not relevant to this in the slightest. Quite clearly rpm is not the upstream
here, it's more like downstream from where this is actually being developed. So
we could also sync just the script itself, knowing that upstream has its own
tests and we're just a distributor. Which opens the question of whether this is
a meaningful arrangement again.
I suppose the path of least resistance, at least short-term (think rpm 4.16),
would be to acknowledge the actual development model for what it is and just
pull the script changes into rpm without the tests.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1195#issuecomment-633836608
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
