--=-V3ChPQ9AYzmW0gkiVThn
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2008-05-05 at 23:42 -0700, Ade Lovett wrote:
> Hi Folks,
>=20
> Is there any particular reason both evolution and evolution-exchange =20
> hard code the berkeleydb version to 41?
>=20
> I've been running it with 4.4 for quite some time now with no ill =20
> effects, so perhaps changing:
>=20
> USE_BDB_VER=3D 41
>=20
> to
> USE_BDB_VER=3D 41+
>=20
> in the respective Makefiles is in order?


There is an issue about compatibility. That is, if one starts using
4.1, then moves to 4.4, the underlying database may not work properly as
no conversion steps are taken. Historically, e-d-s always used 3.x (and
internal copy). But we found we could move to 4.1, and link
dynamically. If we were to relax the DB dependency, we would need
confirmation that we can move from 4.1 to 4.4 safely.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-V3ChPQ9AYzmW0gkiVThn
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkgkqhsACgkQb2iPiv4Uz4d97gCfZ8fgLJTc3t ONBO4obgrbzbyn
pwUAmwUFUGNXHPejqzDzcoFif/fPOljf
=5+Qo
-----END PGP SIGNATURE-----

--=-V3ChPQ9AYzmW0gkiVThn--