KDE/kdepimlibs

[Andreas Pakulat]

On 08.12.07 16:45:42, Christian Ehrlicher wrote:
> Allen Winter schrieb:
> > On Saturday 08 December 2007 12:20:17 Marc Mutz wrote:
> >> You just disabled something for everyone that otherwise disables
> > itself when
> >> _necessary_. I'm not making policies, but to me that looks like a politic
> >> statement. Fine. Problem: The people you want this to read won't, anyway.
> > 
> >> Your call.
> > 
> > Can someone summarize the issue here?
> > I don't understand what all the arguing is about.
> > The stack looks like this, AFACIT:
> > 
> > gpgme
> > gpgme++ (in kdepimlibs)
> > qgpgme (in kdepimlibs)
> > kmail,etc (in kdepim)
> > 
> > Seems to me that if gpgme is available for Windows, and if gpgme++ and
> > qgpgme are
> > ported to Windows, then we can build kmail,etc for Windows.
> > Christian told me that gpgme is available for Windows, right?
> > Does gpgme++ and qgpgme work for Windows?
> > 
> > What am I missing?
> > 
> This missing point was - I was wrong because kdepimlibs did not compile
> for a long time because of missing hard dependency gpgme-qt (it's
> currently developed in gpgme svn, no official release yet, nothing about
> this anywhere).

So kdepimlibs can't compile without gpgme*? Or are they just useless
without that part of the libs? If gpgme is an optional part of the
module, not needed for kdebase (even if its needed for kdepim things)
then the addition of gpgme should depend on wether gpgme libs are found
or not. Thats currently not done.

If however the gpgme-stuff in kdepimlibs is not optional and needs to be
compiled, the if() from Christian is correct and needs to stay until
there's an official release from gpgme that at least builds properly
with mingw. Ideally it would also build with msvc at that point.

Andreas

-- 
Your boss climbed the corporate ladder, wrong by wrong.