Re: [Monotone-devel] nvm.stripped on Win32 MinGW; Botan

[Markus Wanner]

Hi,

Stephen Leake wrote:
> m4/botan.m4 says we need botan > 1.6.3, but not 1.7.14.
> 
> However, on debian, I have 1.7.8-3, which configure accepts, but at
> runtime mtn says we need 1.7.22.

What botan version did you compile against? (mtn version --full)

Hm.. I've corrected the INSTALL document to say: botan 1.6.3, which is
the minimum requirement (and that seems sane, as fc9, Gentoo, FreeBSD,
Debian Etch all have that).

Depending on what botan version you *compile* against, the resulting
monotone binary is compatible with either:

 * botan 1.6.3 - 1.7.5 (A)
 * or botan 1.7.6 - 1.8.x (B)
 * or botan 1.7.22 - 1.8.x (C)

As 1.7.x is a development branch, we cannot rely on its API stability.
However, only changes in version 1.7.6 really affect us.

AFAICT, 1.7.22 brings new sha1 core selection features (which obviously
also made it into 1.8.x), used by benchmark_sha1 *if compiled against
1.7.22 or higher* (variant C).

As botan 1.8.x is stable now, I think it's worth providing that
additional facility and break compatibility with 1.7.21 and before.
Those version should IMO not be used on a stable system anyway.

> On the botan website, I can download 1.8.0 or 1.6.5. I gather I should
> use 1.8.0, for both Debian and Windows MinGW.
> 
> Should I also fix m4/botan.m4 to require > 1.7.21? or >= 1.8.0?

No, certainly not. I've tested m4/botan.m4 with pretty much all botan
versions since 1.6.3 on Debian.

If you've compiled against some botan 1.7.21 or before and the resulting
binary want 1.7.22, that's a bug in monotone.cc. But I've just rechecked
and very much doubt that.

Regards

Markus Wanner