tdb_chainlock() in tdb1, tdb2 and tdb_compat ?

[Jeremy Allison]

On Thu, May 10, 2012 at 08:35:07AM -0400, simo wrote:
> 
> Rusty,
> it is a big change for external users of tdb.
> Distributions ship tdb1 as a standalone library. If you force only tdb2
> and at the same time you do not rename all the symbols and force API
> changes you are putting distributions between a rock and a hard place.
> 
> I really think we should change API signatures so tdb1 and tdb2 (or
> whatever we want to call it) can be installed side by side for a while
> until all users decide to abandon tdb1 and we can kill it.

+1 on this. It's the only manageable way to make a transition.

Jeremy.