libgmime installation and build requirements

[Scott Lenser]

> I'm not in favor of libgmime:
> 
> * It's oversized.
>   We don't need the encoding stuff.
>   We don't need uudecode.
>   We don't need signature handling.
> 

True, we don't need the encoding stuff.  OTOH, the fact that I don't need
every widget known to man doesn't keep me from using GTK.

Greg has found instances of uuencoded attachments show we do need
uudecode.

We don't need signature handling.

> * I cannot build 1.0.6.
> 
> * I cannot build 2-current from CVS, it's inconsistent at best, old
>   libtool fails to build shared library, new libtool/automake break the
>   build altogether.
> 

I'm not sure why you are having so much trouble.  I just had to install
libglib-2.0 and dev package and was able to build and install with no
problems.

> * Why does it need glib to build if it doesn't use it at run time?
> 

It uses glib at runtime.  It's listed in the ldd output for my version
which uses libgmime.

> We're calling for MAJOR complaints by users if we go for libgmime and
> pull all its gory build dependencies in.
> 
> -- 
> Matthias Andree
> 

What gory dependencies?  It depends on libc6 (for iconv) and glib-2.0
(which lots of other stuff depends on).

- Scott