Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Mikhail Teterin]

понеділок 06 березень 2006 10:28, Jeffrey Stedfast Ви написали:
> Back when I was still on the project, the problem was that users could
> not migrate their data between different machines running different
> distributions (or different versions of the same distribution) because
> of file format changes that were continuously happening in libdb (even
> between minor revisions of libdb!!! - e.g. libdb-3.1.17 was not
> compatable even with 3.0.x or 3.2.x)

Is not this problem solved long ago by db_upgrade, that comes with libdb-4.x 
versions?

-mi
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Jeffrey Stedfast]

On Mon, 2006-03-13 at 13:48 -0500, Mikhail Teterin wrote:
> понеділок 06 березень 2006 10:28, Jeffrey Stedfast Ви написали:
> > Back when I was still on the project, the problem was that users could
> > not migrate their data between different machines running different
> > distributions (or different versions of the same distribution) because
> > of file format changes that were continuously happening in libdb (even
> > between minor revisions of libdb!!! - e.g. libdb-3.1.17 was not
> > compatable even with 3.0.x or 3.2.x)
> 
> Is not this problem solved long ago by db_upgrade, that comes with libdb-4.x 
> versions?

No.

> 
>   -mi
> 
-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED]  - www.novell.com

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Jeffrey Stedfast]

Back when I was still on the project, the problem was that users could
not migrate their data between different machines running different
distributions (or different versions of the same distribution) because
of file format changes that were continuously happening in libdb (even
between minor revisions of libdb!!! - e.g. libdb-3.1.17 was not
compatable even with 3.0.x or 3.2.x)

Hence we started forcing libdb-3.1.17 (and later we moved to 4.1 - I
don't remember why)

Jeff

On Mon, 2006-02-27 at 17:49 -0500, Mikhail Teterin wrote:
> Hello!
> 
> I'm trying to convince the maintainers of the evolution-data-server
> FreeBSD port ()
> to build the software against the db4-version installed by the separate
> port of SleepyCat's db4 ().
> 
> I'm using the thus built evolution (against db-4.3.29) to type this
> message, but they remain hesitant, because of the past problems they
> encountered trying to build evolution using the already installed db3
> instead of the version then-bundled with evolution.
> 
> I'm guessing, you used to have modified version of db3, which allowed it
> to work, where the "standard" version did not. Is there anything like
> that in the db4.1 version bundled with e-d-s 1.4.2.1, or can we safely
> use any reasonably recent version of db4?
> 
> Moreover, perhaps, you can be convinced to stop the bundling of db4
> completely and turn it into just another pre-requisite?
> 
> Thanks! Yours,
> 
>   -mi
> 
> ___
> Evolution-hackers mailing list
> Evolution-hackers@gnome.org
> http://mail.gnome.org/mailman/listinfo/evolution-hackers
> 
-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED]  - www.novell.com

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Mikhail Zabaluev]

В Пнд, 06/03/2006 в 09:25 +, Ross Burton пишет:
> http://bugzilla.gnome.org/show_bug.cgi?id=319393 contains a patch we've
> been using in the DBus port of EDS to use a dynamic libdb.  Instead of
> simply hacking away at the makefiles it adds an option, so is suitable
> for integration.
> 
> EDS comes with a copy of libdb 4.1.  It was copied as back in the early
> days of Evolution some people had db3, and some had db4, but the file
> format changed.  The solution to this was to add migration logic from
> db3 to db4 in EDS, and to enforce EDS linking to db4.1 by embedding the
> source.
> 
> Recently the DB file format hasn't changed, so the problem is moot.
> I've been running EDS with a dynamically linked libdb 4.1, 4.2 and 4.3
> without any problems, on both Intel and ARM.

Within a distribution, we can enforce dynamic DB linkage as we see fit.
So, I presume, it's safe to apply this patch in a package and save a bit
on memory footprint, plus get all the recent DB bug fixes.

Thank you, Ross, for clarifying the matter.

> I really would like this patch to be merged into EDS for G2.16, if only
> for the memory reduction: libdb is statically linked into both the bdb
> addressbook backend and libedataserver, at a cost of 600K each time.

I'll second that.


___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Ross Burton]

On Mon, 2006-02-27 at 17:49 -0500, Mikhail Teterin wrote:
> Hello!
> 
> I'm trying to convince the maintainers of the evolution-data-server
> FreeBSD port ()
> to build the software against the db4-version installed by the separate
> port of SleepyCat's db4 ().
> 
> I'm using the thus built evolution (against db-4.3.29) to type this
> message, but they remain hesitant, because of the past problems they
> encountered trying to build evolution using the already installed db3
> instead of the version then-bundled with evolution.
> 
> I'm guessing, you used to have modified version of db3, which allowed it
> to work, where the "standard" version did not. Is there anything like
> that in the db4.1 version bundled with e-d-s 1.4.2.1, or can we safely
> use any reasonably recent version of db4?
> 
> Moreover, perhaps, you can be convinced to stop the bundling of db4
> completely and turn it into just another pre-requisite?

http://bugzilla.gnome.org/show_bug.cgi?id=319393 contains a patch we've
been using in the DBus port of EDS to use a dynamic libdb.  Instead of
simply hacking away at the makefiles it adds an option, so is suitable
for integration.

EDS comes with a copy of libdb 4.1.  It was copied as back in the early
days of Evolution some people had db3, and some had db4, but the file
format changed.  The solution to this was to add migration logic from
db3 to db4 in EDS, and to enforce EDS linking to db4.1 by embedding the
source.

Recently the DB file format hasn't changed, so the problem is moot.
I've been running EDS with a dynamically linked libdb 4.1, 4.2 and 4.3
without any problems, on both Intel and ARM.

I really would like this patch to be merged into EDS for G2.16, if only
for the memory reduction: libdb is statically linked into both the bdb
addressbook backend and libedataserver, at a cost of 600K each time.

Ross
-- 
Ross Burton mail: [EMAIL PROTECTED]
  jabber: [EMAIL PROTECTED]
 www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF



signature.asc
Description: This is a digitally signed message part
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Tor Lillqvist]

As far as I can recall, when I asked the same thing, the response was
that this is how Berkeley DB is supposed to be used, "embedded" into
another product. That some (all?) Linux distributions choose to also
ship a separately installed instance was irrelevant ;)

--tml


___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Peter Colijn]

On 3/6/06, Mikhail Zabaluev <[EMAIL PROTECTED]> wrote:
> I used to compile e-d-s 1.4 along an external db4.3, by applying a
> simple patch. It didn't seem to cause any problems.

You are of course free to apply your own patches; however, in the long
term, using a distribution's version of bdb will probably be an
intolerable maintenance burden for either distributors or evolution:

> So, what's the purpose of bundling an obsolete version of Berkeley DB
> inside the project?

I think the idea was that since the berkeley db API is not very
stable, and since distributions ship a wide variety of versions of
berkeley db, it would be simpler to ship a version of bdb along with
evolution to avoid either

(1) requiring distributions wishing to ship evolution to either ship a
special bdb just for it, or patch evolution on their own (a big
maintenance burden for distributors)

or

(2) requiring evolution to be compatible against multiple versions of
bdb (a big maintenance burden for evolution)

Maybe the bdb API is more stable these days so this no longer makes
sense; I was under the impression it was still changing quite often.

Have fun,

Peter
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] building evolution-data-server against the already installed libdb

[Mikhail Zabaluev]

В Пнд, 27/02/2006 в 17:49 -0500, Mikhail Teterin пишет:
> I'm trying to convince the maintainers of the evolution-data-server
> FreeBSD port ()
> to build the software against the db4-version installed by the separate
> port of SleepyCat's db4 ().
> 
> I'm using the thus built evolution (against db-4.3.29) to type this
> message, but they remain hesitant, because of the past problems they
> encountered trying to build evolution using the already installed db3
> instead of the version then-bundled with evolution.
> 
> I'm guessing, you used to have modified version of db3, which allowed it
> to work, where the "standard" version did not. Is there anything like
> that in the db4.1 version bundled with e-d-s 1.4.2.1, or can we safely
> use any reasonably recent version of db4?
> 
> Moreover, perhaps, you can be convinced to stop the bundling of db4
> completely and turn it into just another pre-requisite?

I used to compile e-d-s 1.4 along an external db4.3, by applying a
simple patch. It didn't seem to cause any problems.
So, what's the purpose of bundling an obsolete version of Berkeley DB
inside the project?
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

[Evolution-hackers] building evolution-data-server against the already installed libdb

[Mikhail Teterin]

Hello!

I'm trying to convince the maintainers of the evolution-data-server
FreeBSD port ()
to build the software against the db4-version installed by the separate
port of SleepyCat's db4 ().

I'm using the thus built evolution (against db-4.3.29) to type this
message, but they remain hesitant, because of the past problems they
encountered trying to build evolution using the already installed db3
instead of the version then-bundled with evolution.

I'm guessing, you used to have modified version of db3, which allowed it
to work, where the "standard" version did not. Is there anything like
that in the db4.1 version bundled with e-d-s 1.4.2.1, or can we safely
use any reasonably recent version of db4?

Moreover, perhaps, you can be convinced to stop the bundling of db4
completely and turn it into just another pre-requisite?

Thanks! Yours,

-mi

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers