[Kde-pim] Possible API compatibility issue?

Sune Vuorela nospam at vuorela.dk
Tue Dec 1 10:02:59 GMT 2009


On 2009-12-01, Volker Krause <vkrause at kde.org> wrote:
> --===============1836359070==
> Content-Type: multipart/signed;
>   boundary="nextPart2509631.QOQInlatzN";
>   protocol="application/pgp-signature";
>   micalg=pgp-sha1
> Content-Transfer-Encoding: 7bit
>
> --nextPart2509631.QOQInlatzN
> Content-Type: text/plain;
>   charset="utf-8"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> On Tuesday 01 December 2009 05:48:51 Christoph Feck wrote:
>> Since a few days, I am getting the attached build error, but there were no
>> changes in playground/office/kmymoney. I contacted the author of KMyMoney,
>> and he said r986589 is the cause for this error, but he does not use trunk
>> yet.
>>
>> So it looks like there is some incompatible change in kdepim, but I am not
>> sure if the API used there is public at all. Please have a look at it.
>
> nothing in kdepim is public API, that's what we have kdepimlibs for. In fac=
> t,=20
> I'm surprised these headers are installed at all.

At least in debian, we have no development packages for kdepim, so this
will make kmymoney impossible to ship with all features.

/Sune

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/



More information about the kde-pim mailing list