On Tue, 2008-10-07 at 09:44 +0200, Wolfram Schlich wrote:
Most of it is probably the configure script. I'd be happy to clear out the libdbi pecularities wrt syslog-ng 2.1 as well.
My patches have already been integrated in libdbi since, so it should be easy to port to the latest libdbi upstream.
The things that we did in our version: * we renamed dbi to dbi-0.8 in order not to clash with a local libdbi package, this affected: * .deb packages * dbi-0.8.pc * various files the package installs /usr/lib/libdbd-0.8 for instance * currently the only things that prevents syslog-ng to be compiled against the upstream libdbi are: * we should search for dbi.pc instead of dbi-0.8.pc * the dbi package does not install the .pc file automatically (e.g. there's no Makefile rule to install that), nevertheless the file is generated by its configure script.
This patch against syslog-ng will make it look for the upstream libdbi: [...] After that it should work.
Yep, it does. Thanks! Compiled fine against libdbi 0.8.3.
Please note that we submitted a couple of patches against libdbi/libdbi-drivers, so make sure that you use the latest CVS version.
Hmm. What about 0.8.3, is it sufficient?! Otherwise I'd have to create a CVS snapshot + ebuild for libdbi and libdbi-drivers which I'd prefer not to do ;) What were those patches about anyway? Performance? Is syslog-ng SQL support kinda unusable/unstable without them?
Well, I remember some leak fixes in sqlite3 driver, the ability to return the record type information in sqlite3 (was done Markus), just please check out the CVS changelog, it should contain entries for the changes I've made. I still have some local changes pending, but those are HP-UX related. I hope to submit those as well in the future. -- Bazsi