Given that 1.8.3-3 and 1.8.3-4 contain incompatible dlls, isn't the tradition to name the packages differently and have them coexist in setup for a while (without default upgrading when in non-test mode)?
That way old applications can keep working when gdbm is updated and rebuilding the databases is only necessary when the relevant application (exim, cvs,...) is updated to use the new gdbm.
Yes, it is -- and that is what I did.
The old dll was/is named cyggdbm-3.dll and is in the libgdbm3 package. The new dll is named cyggdbm-4.dll and is in the libgdbm4 package.
What's the problem?
-- Chuck
