Re: Problems with autopackage and qt4

On Mon, May 18, 2009 at 3:00 PM, Juan Francisco Cantero Hurtado
<[email protected]> wrote:
> Any idea about my problems with qt4 and requireAtLeast?
>

My memory may fail me here, but I think this is the issue:
requireAtLeast is a bit poorly named. One would think it does the same
as require but also accepts higher versions. This is not what it does
:)

requireAtLeast works against the SOFTWARE_VERSION information of a
skeleton, while require works against the INTERFACE_VERSION. The
difference here is that SOFTWARE_VERSION reflects the version of the
software ("duh") which typically is the same version you see on that
softwares web page or in the normal package manager. The
INTERFACE_VERSION, on the other hand, corresponds to the features
supported by the skeleton (or rather, the library it represents).

Let's take an fake example
libFoo v1.0 is the first release. both INTERFACE_ and SOFTWARE_VERSION is 1.0
libFoo v1.1 fixes some bugs, bumping SOFTWARE_VERSION to 1.1 but keep
INTERFACE_VERSION at 1.0 since nothing has changed to its interface
libFool v1.2 fixes bugs and adds new features, bumping
SOFTWARE_VERSION to 1.2 and INTERFACE_VERSION to 2.0 (since perhaps it
broke compability or something)
....a few years down the line....
libFoo v10.5 is released, with SOFTWARE_VERSION set to 10.5 and
INTERFACE_VERSION 1.8

So, "Software version" is the version of the software, incremented
with every release, while INTERFACE_VERSION represents version of the
API/ABI and is incremented in every release *that changes the API or
ABI*

hope this explains a bit

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]