After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347895 - EDS should install libdb to private directory
EDS should install libdb to private directory
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: general
1.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-07-18 10:16 UTC by Ross Burton
Modified: 2009-10-02 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ross Burton 2006-07-18 10:16:27 UTC
EDS is currently statically linking to libdb-4.1.la in four places:

* the file backend
* the groupwise backend
* libedataserver
* libedata-book

Now libdb-4.1.a is a 600K library, so this is 1800K more than is required.  When a non-system libdb is used, instead of statically linking EDS should install it to $prefix/lib/evolution-data-server/libdb-4.1.so.  This way EDS can use a known-good version of libdb, but large amounts of memory isn't wasted.
Comment 1 André Klapper 2006-08-28 13:07:59 UTC
hmm... didn't we do something about this?
Comment 2 Matthew Barnes 2006-08-28 13:50:39 UTC
Yes, it was fixed in 1.7.90.
See bug #319393, bug #344693, and bug #347891.
Comment 3 Matthew Barnes 2006-08-28 14:03:07 UTC
Then again, maybe not.

The --with-libdb configure option got fixed in 1.7.90.  That option is for dynamically linking to the system's libdb.  This bug is about how to link to the version of libdb that comes packaged with EDS for when --with-libdb is NOT used.  Not sure if it's been addressed yet but it's a good idea.
Comment 4 Matthew Barnes 2008-03-11 00:58:58 UTC
Bumping version to a stable release.
Comment 5 Ross Burton 2008-04-24 13:36:13 UTC
Actually, can we just stop shipping libdb?  Debian, Ubuntu and Fedora use --with-libdb and we haven't had any complaints from them.  Dropping it will save lots of disk space, and save us the hastle of maintaing a libdb fork.
Comment 6 Matthew Barnes 2008-04-24 14:42:19 UTC
(In reply to comment #5)
> Actually, can we just stop shipping libdb?

+1  Plus it will fix quite a few distcheck errors if you configure --with-libdb.
Comment 7 Ross Burton 2009-10-02 11:38:19 UTC
This is fixed now that we don't ship a private libdb any more.