On Saturday 30 June 2007, Allen Winter wrote:
> On Saturday 30 June 2007 04:49:20 pm David Faure wrote:
> > On Saturday 30 June 2007, Tom Albers wrote:
> > > SVN commit 681873 by toma:
> > > 
> > > KGPG comming from kdepim.
> > > - install headers
> > > - separate debug area's.
> > > 
> > 
> > Hmm. Don't we want to get rid of this code (in favour of qgpgme), ideally?
> > 
> Doesn't sound familiar, but possibly.

We need to port some kgpg-using code to libkleo before we can get rid of libkpgp in kmail,
but since that's the plan anyhow, this tells me that kpgp should probably not be in kdepimlibs.

> Are you suggesting to do away with PGP support?  Or does GPG also do PGP?
Hmm, major confusion here... Either by you or by me ;)
From what I know (and which wikipedia seems to confirm) :
  OpenPGP is the (IETF-standard) protocol.
  GPG ("gnupg" binary, gpgme library) is the GNU implementation of that protocol.
  PGP ("pgp" binary) is the implementation by Philip Zimmermann (which predates GPG, but has unclear status wrt patents)

... and libkpgp launches either gnupg or pgp (configurable). So libkpgp has support for both
implementations indeed, but I don't think this is relevant anymore. Certainly nobody is missing
the PGP support when sending encrypted mails (which has been using libkleo for a long time,
i.e. gpgme for the OpenPGP support).

So by not using libkpgp anymore we don't lose any support for any actual crypto protocol,
we only lose support for a not-really-opensource backend which we don't need since
the GPG implementation comes with the same features and everyone uses GPG nowadays...

Using a library (like kleo does) is certainly much nicer than executing a separate binary (like libkpgp does),
for many reasons (speed, stability, integration etc. etc.)

-- 
David Faure, faure@kde.org, dfaure@klaralvdalens-datakonsult.se
KDE/KOffice developer, Qt consultancy projects
Klarälvdalens Datakonsult AB, Platform-independent software solutions