Module submission - gnupg-1.9.x

[Zbigniew Luszpinski]

> On Tue, 14 Mar 2006 01:51:37 +0100, Zbigniew Luszpinski <zbiggy at o2.pl> 
wrote:
> > module name       : gnupg-1.9.x
> > suggested section : crypto
> > update (y/n)      : n
> > bugfix (y/n)      : n
> > security (y/n)    : n
> >
> > This patch will force gnupg-1.9.x module to rebuild gpgme module to
> > activate
> > gnupg-1.9 extensions in gpgme. There is no conflict with classic gnupg.
> > This is required for incoming kdepim3 module update which will enable
> > optional
> > e-mail cryptography plugins.
> >
> > greets,
> > Zbigniew 'zbiggy' Luszpinski
>
> you should replace the forced compile with an integrity check instead:
>
> if module_installed X ; then
>     lunar fix X
> fi
>
> this skips recompiles in case the binary linking isn't broken - and is the
> most flexible and fast way.
>
> Auke

In this case forced rebuild is unfortunatly required. I made gnupg-1.9.x 
additional in lunar to prevent conflict with classic/stable gnupg. This is 
right choice as gnupg-1.9 is development (but has extensions missing in 
classic gnupg) release of gnupg till it reaches 2.0 version. gpgme works with 
classic gnupg in general and can be build without 1.9 version (if it is not 
installed before gpgme compilation). Installation of gnupg-1.9.x does not 
change anything in relation with gpgme (gpgme simply ignores existence of 1.9 
extensions). Thus forced compilation of gpgme is required to make it see 1.9 
extensions. lunar fix will not fix anything because nothing is broken (it is 
up to gpgme if it uses _optional_ 1.9 or not). Existence of 1.9 extensions is 
only checked during configure part of gpgme compilation and decision if 
extensions support will be enabled is taken at this step only. Look at 
compile log of gpgme to see detection report. I'm sure your idea is very good 
and will remember it for future, but in this case it is impossible to work - 
gpgme is never rebuild.

greets,
Zbigniew 'zbiggy' Luszpinski