On Thursday, 3 November 2016 at 11:45, Sandro Knauß wrote:
> You may got the notice, that the cpp(gpgme++) and qt (QGpgme) interface,
> previously build by KDEPIM in the libgpgmepp package, moved down to GpgME
> directly. That's why KDEPIM depends on very recent GpgME.
>
> Together with Andre
On jeudi 3 novembre 2016 21:25:45 CET Andre Heinecke wrote:
> Because the
> overall maintainer of gpgme thinks that pkg-config is an unportable devilish
> thing, created by these young people who don't care about compatibility
> with systems from the 70'ies, just like cmake . So if I can get in a
Hi,
On Thursday 03 November 2016 18:57:34 Rolf Eike Beer wrote:
> Am Donnerstag, 3. November 2016, 11:45:47 schrieb Sandro Knauß:
> That's good news from my (KGpg) point of view, as we were recently in a
> discussion which versions we need to support. We do not need gpgme itself,
> but we use the
Hey,
> That's good news from my (KGpg) point of view, as we were recently in a
> discussion which versions we need to support. We do not need gpgme itself,
> but we use the headers to get some algorithm defines.
>
> Does that version of GpgME bring a CMake config file with it so we can drop
>
Am Donnerstag, 3. November 2016, 11:45:47 schrieb Sandro Knauß:
> Hey,
>
> Together with Andre Heinecke (developer of gpgme), we discussed the minimum
> version of GpgME we want to support with the upcoming release of KDEPIM for
> Applications 16.12.
>
> You may got the notice, that the
