Build verification against actual required minimal versions
In autoconf (and debian/control) we state minimum versions of required upstream packages.
A job to actually install those minimum versions and check the build would be needed in order to make sure we don't break this.
So if osmo-bsc uses a function from libosmo-mgcp, and configure.ac states libosmo-mgcp >= 1.0.0, then we should build + install the 1.0.0 tag of libosmo-mgcp and attempt the osmo-bsc build.If the build fails, the patch should IMHO not get a V+1 but remain rejected until
- a new version of the library has been tagged
- the patch is updated to update the requirement to that new version in configure.ac
I know this imposes some more obstacles in the development process, but the existing way of handling things is a constant neglect of our users and proper dependency management in distributions and elsewhere.
- Status changed from New to Rejected
Well, strictly speaking this issue talks also about
Is this actually a full-on duplicate of #2642, or is there a subtle difference that evades me?
- debian minimal version requirements (not just autoconf)
- integrating this in our gerrit build testing
But I think we can live without those two for now, the important part has been resolved in #2642