[Kde-pim] Kleopatra / GpgME++ maintainership

Andre Heinecke aheinecke at intevation.de
Tue Oct 13 22:45:00 BST 2015


Hi,

On Tuesday 13 October 2015 22:59:04 Sandro Knauß wrote:
> Hi,
> 
> > After maintaining Kleopatra as part of Gpg4win since 2013 I'd like to
> > officially take over the maintainership of Kleopatra and Gpgme++.
> 
> gratulations! I didn't knew some month ago, that kleopatra is that
> widespread in the windows world.

And with our work on GpgOL[1] it looks good that Kleopatra will become a 
decent (full MIME Support) crypto provider for the most used Desktop MUA, 
which sadly still is Outlook. That should help to spread it even further :-)

> I really like your ideas for improving kleopatra.

Great to hear.

> > I'd also like to move libkleo and Kleopatra out of the main kdepim
> > repository as I think it makes sense and it would help with dependency
> > management without something like the old KDEPIM_ONLY_KLEO hack. :-)
> > 
> > libkleo should imo also become a framework library with a stable API, as
> > already suggested in the kdepim tasks.
> 
> I think the splitting is the right step forward - especially making libkleo
> a frameworks sounds good, if the interface is really stable.

I think so. I'd prefer to keep this stable (backwards compatible) as the API 
has proven itself over the years.

> One issue poped up in the last month, when trying to compile kontact
> together with gnupg is that the way of compiling is different for gpg4win
> than our build setup (emerge). Kontact is also using libkleo&gpgme++ for
> crypto support, so we need to make sure, that kleopatra and kontact can be
> compiled both on windows and play together. Is there a way to make sure,
> that kontact can use libkleo without compiling it on its own? 

Yes if you use Mingw with a compatible GCC.

For MSVC I'd say No. As a second thought. [2] "Maybe" Libkleo uses exceptions. 
This will not be compatible but as a Qt hacker I'm not fond of exceptions and 
usually don't use them. But removing them would break API compatibility as 
mentioned above ;-) 

While there are some other issues with C++ Compiler ABI compatibility for 
Gpgme++ I think we should be able to deal with it.

I can think of the solution:
 - Gpg4win provides a gpgme++ dev package when necessary.
 - You build Kdepim and libkleo with MSVC against that package.

This would basically be the same we do now. Any libraries developed by the 
GnuPG Project won't support MSVC or builds on Windows (It's out of my hands to 
change this). So currently we create a binary package under GNU/Linux and 
include this in the Emerge build of Kdepim. Then we upload that binary package 
of Kleopatra and include it in the Gpg4win installer build system.


For the Future I want to drop the Emerge (building on Windows) step of that 
and just cross compile all required libraries and Kleopatra in the Gpg4win 
buildsystem. Because the current process is not Hacker friendly, intransparent 
and basically a pain to maintain.

> Also with the movement of a mobile kontact version, we may also look 
> into the  requirements to compile it there. But Gpg4All also want to address 
> mobile devices, so there is no big difference in the goals...

In Gpg4all we are mainly focusing on studies / concepts regarding OpenPGP (not 
limited to GnuPG) on Android and in Browsers.
There will be (thankfully) no Kleopatra Mobile in this Project.

Regards,
Andre

1: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgol.git;a=shortlog;h=refs/heads/mime-addin
2: 
http://www.mingw.org/wiki/Interoperability_of_Libraries_Created_by_Different_Compiler_Brands

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20151013/e7cfef3f/attachment.sig>
-------------- next part --------------
_______________________________________________
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