Project

General

Profile

Feature #2627

Build verification against actual required minimal versions

Added by laforge 15 days ago.

Status:
New
Priority:
Normal
Assignee:
Osmocom Developers
Category:
jenkins
Target version:
-
Start date:
11/08/2017
Due date:
% Done:

0%

Spec Reference:

Description

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
  1. a new version of the library has been tagged
  2. 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.

Also available in: Atom PDF