Version: 0.7 (using KDE 3.3.2, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-6) OS: Linux (i686) release 2.6.10-1-686 Wish: using a sqlite already on the system makes digikam (pkgs) smaller and is easier to handle in case of sqlite bugs/security fixes. (Think about the mess the xdpf bugs, were several pkgs had to be updated because the used a xdpf source copy;) Achim
> using a sqlite already on the system > makes digikam (pkgs) smaller and is > easier to handle in case of sqlite > bugs/security fixes. As was eplained in thread on kde-devel, not always external packages have all features of sqlite needed by digikam. Moreover - for example Mandrake doesn't include Qt sqlite interface into main distro packages. Also digiKam development is moving quite fast and not everywhere is already sqlite3.
Hi Mikolaj, > As was eplained in thread on kde-devel, not always external packages > have all features of sqlite needed by digikam. Moreover - for example sorry for not being precise enough. I didn't want to replace it, only a possibility to use it alternatively with default use included sqlite (I also changed the prio of the wish to low). Renchi mentioned that SuSE uses a patch to use an external sqlite. The topic is low prioity (even for me) but maybe I'll try it one day. AFAIU Renchi he does like to support a --with-included-sqlite[=yes] configure switch (he knows for sure better the possible troubles that can happen!). It's fine with me to keep this wishlist open just as a reminder and if sqlite things settle reconsider an optional switch for external sqlite usage. > Mandrake doesn't include Qt sqlite interface into main distro packages. > Also digiKam development is moving quite fast and not everywhere is > already sqlite3. Absolutely off topci but related ;) just saw this when I upgraded my debian sarge system today ;) ... amorak 1.1.1-2 ... + SQLite 3 is now in the archive: - changed Build-Depends on libsqlite0-dev to libsqlite3-dev. - pass --without-included-sqlite to ./configure. - patch configure.in to check for sqlite3 (>= 3.0). Upstream forgot to update this check in the 1.1 series. [sqlite3_in_configure.in.patch] ... ;) Achim
i think you have misunderstood me. i'm _not_ in favor of including external sqlite support for reasons of a) thread-support b) utf-8 support not being available in many external sqlite libraries. suse does make use of a patch to support external sqlite. its for the packagers to decide whether they want to do the same. but it will not be a supported option from within digikam