Re: complex versioning scenario

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
> We've a complex versioning scenario here which leads me to my limits. :(
> 
> There are two recipes. One for a shared library and one for an application using this library.
> 
> Both use GNU autotools (so they have internal version information). For continuous integration purposes both use AUTOREV.
> 
> At the moment the recipes look like this:
> 
> 
> ------------ libfoo_git.bb -------------
> PR = "r7"
> PE = "2"
> SRCREV="${AUTOREV}"
> PV = "gitr${SRCPV}"
> ...
> 
> 
> ------------ app_git.bb ----------------
> DEPENDS = "... libfoo ..."
> PR = "r10"
> PE = "1"
> SRCREV="${AUTOREV}"
> PV = "gitr${SRCPV}"
> ...
> 
> 
> Now we have the following problem. libfoo has some incompatible
> changes in its interface (a new internal major version).
> 
> In my opinion this should find its represenation in the package
> versioning in a way that the dependency checker can guarantee that the
> library and the application package match each other.

It is generally impossible to directly compare two git hashes and decide
whether one is "greater" than the other. This is why most git recipes
have PV = "0.0+git${SRCPV}" so that you can change 0.0 when something
major changes. That way you can put a constraint in the second recipe.

This is a fundamental problem with git versioning and not something we
can fix generically.

Cheers,

Richard