Re: Upcoming GMime 3.0 changes

[Peter Bloomfield <PeterBloomfield bellsouth net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All:

On 03/14/2017 02:14:18 PM Tue, Albrecht Dreß wrote:
> Hi Jeff:
>
> Thank you so much for this information!
>
> I believe your new lib will simplify many parts in Balsa (but we probably still need to support the old GMime 
> 2.6 based stuff until all LTS distos switched to the new one).

I installed GMime 3.0.1 from git, and I have a patch against Balsa git master for building with it, keeping 
the ability to build with 2.6 through the magic of #if. It just adapts Balsa's current code to work with the 
new API, but even so it's a big mess, over 2k lines of patch, touching 32 files and creating 160 blocks of 
conditionally compiled code. But it compiles and runs in at least one configuration, so it's available for 
exploring the new features that Jeff put in 3.0.

If we're going to need a single tree that can build with either 2.6 or 3.0, I could commit this patch. It 
looks first for 3.0, with a fallback to 2.6--no configure option for choosing, although one could be 
implemented. Alternatively, we could make a stable gmime-2.6 branch and make master 3.0-only, which would 
make for a more convenient development process.

Since no GMime 3.0 packages have yet been released(?), and development is possible only for the intrepid git 
user, another possibility would be to open a bug and post patches there, until released packages enable 
easier testing.

Any suggestions about how to proceed?

Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAllK0QQACgkQH1/UtbkqdPWangCfWRoeXDTIP1jS39YwI1LKebYF
yOYAn3yTAaxv/NKGncKqkDjVmeaqOXzu
=vi+P
-----END PGP SIGNATURE-----