Re: [Patch] Improve low-level network library, POP3 responsiveness on error

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

Hi Albrecht:

On 01/25/2018 03:16:38 PM Thu, Albrecht Dreß wrote:
> Hi Peter:
> 
> Am 23.01.18 02:58 schrieb(en) Peter Bloomfield:
>> I wish I could! My education has come from too many hours scrutinizing <URL:<http://mesonbuild.com/Manual.html>. I started with <URL:http://mesonbuild.com/Porting-from-autotools.html#porting-from-autotools>, but while it gives a sampler of how to port, it's very incomplete. Seems like it's still evolving!
> 
> Thanks a lot for these links.  Using the Ubuntu 16.04 Meson package failed with the following error:
> 
> ---8<---------------------------------------------------------------
> albrecht@deneb:~/Balsa/git/balsa_build$ meson ../balsa-master
> The Meson build system
> Version: 0.29.0
> Source dir: /home/albrecht/Balsa/git/balsa-master
> Build dir: /home/albrecht/Balsa/git/balsa_build
> Build type: native build
> 
> Meson encountered an error in file meson.build, line 542, column 49:
> lexer
> ---8<---------------------------------------------------------------

I'm guessing some language feature in Balsa's meson.build was introduced after version 0.29.0, and before 0.37.1, but the output doesn't help locate it! The 'project()' function at the top of meson.build has a meson_version argument that can be used to specify a minimum version. Perhaps, when meson and Balsa's meson files have stabilized, we could find an appropriate specification. As it stands, it looks like '>= 0.37.1' is a candidate.

> After upgrading to the package from Debian Stretch (0.37.1), I could configure, but not build, as Ninja is too old.

Can you also upgrade Ninja from Debian Stretch? Surely Meson and Ninja would be kept compatible in a given distro!

Best,

Peter
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQS030wPRfNNA5alz3MfX9S1uSp09QUCWmpFFAAKCRAfX9S1uSp0
9YamAKCi/CaI4I5x/u/CHOGhphYECSflTwCfbxIwpARyzhvO1Ui7Ey+T0Ic7F+8=
=ISYs
-----END PGP SIGNATURE-----