Re: [Evolution-hackers] db3 and db4

[Christopher Smith <x xman org>]

On Wed, 2003-11-19 at 05:35, JP Rosevear wrote:
> This is the real reasons we need to import it - incompatible db
> formats.  As far as we could tell the DB people change formats between
> minor versions (at least they did for the 3.x series) and then don't
> version the libraries properly so its hard to account for binary
> compatability.  If we dynamic linked it means it might be impossible to
> move you .evolution dir to another machine if that machine's evo was
> linked to an older DB.  I don't want various source trees proliferating
> either, but I don't see a better solution at this point.

For Sleepycat's statements on this:

http://www.sleepycat.com/docs/ref/upgrade/process.html

"Berkeley DB major and minor releases may optionally include changes in
all four areas, that is, the application API, region files, database
formats, and log files may not be backward-compatible with previous
releases."

and

"A Berkeley DB patch release will never modify the API, regions, log
files, or database formats in incompatible ways, and so applications
need only be relinked (or, in the case of a shared library, pointed at
the new version of the shared library) to upgrade to a new release."

I'm not sure what you mean by "they don't version the libraries
properly".

-- 
Christopher Smith <x xman org>