Jim Blandy <firstname.lastname@example.org> writes:
> The Berkeley DB 3.2.9 API isn't compatible with 3.1.17. From the
> 3.2.9 ``ChangeLog'':
> Interface Additions and Changes:
> 6.Add a reference to a DB object as the first argument to four application callback functions (the callback functions set by
> DB->set_bt_compare, DB->set_bt_prefix, DB->set_dup_compare, and
> DB->set_h_hash). [#2179]
> This means that every FS btree that uses a customized sort order needs
> to have its code changed slightly. I've included a patch below.
> Should we simply require Berkeley DB 3.2.9, and declare 3.1.17
I think so. Temporary inconvenience for us now, but it is after all
the wave of the future...
If you want to check in that patch (I think you forgot to include it
in your mail), upgrading shouldn't be too painful for the rest of us.
All tests are known to pass w/ the patch and BDB 3.2.9, right?
Received on Sat Oct 21 14:36:24 2006
This is an archived mail posted to the Subversion Dev