Matthias Klose <[EMAIL PROTECTED]> writes: > emulating the BDB 1.85 API can be done using the db_185.h header of > the libdb4.1-dev package, not sure about the BDB on-disk format.
Emulating the API is irrelevant. In Python 2.3, the bsddb package will emulate the bsddb module API. Using db_185.h of BDB 4.x will still cause creation of BDB 4 data files. So it should *not* be linked to bsddb185. Any installation of bsddb185 needs to guarantee that the files it creates are really 1.85 files. > Is there a similiar workaround for 2.2.3? Of course the bsddb185 > module could be backported. Backporting would only be reasonable if you had a library to link against. If Debian has no library anymore that creates 1.85 data files, there is no point in providing a wrapper module around this non-existing module. > what about deprecating the use of the dbm module upstream for 2.3? No. Most systems offer on-disk compatibility of files created by the ndbm over a long period of time. So the module works just fine, except on Linux. Regards, Martin