[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

[Olivier Blin]

Pascal Terjan <pterjan at gmail.com> writes:

>> So it's seems like this was done deliberately due to a ABI breakage a
>> while ago:
>>
>> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34
>>
>> Now, this is an interesting point (regarding our lib policy) bumping the
>> major for an API change and the minor for an ABI change seems kinda
>> sensible to me. So how should we deal with that in our policy? Just use
>> 0.4 as the "major" value here as Christiaan suggested?
>
> A minor change is supposed to only add interfaces and be backwards
> compatible, that's why it is not in the soname.
> If there has been an ABI breakage, the major should be incremented.

If the ABI change occurs in a development or unstable version, it is
normal to break it without bumping the major.

Is this attica release considered stable?

-- 
Olivier Blin - blino