Dear digikam developers, you probably all know about the "bundling/unbundling debate" by now. To keep things constructive, I'd like to ask you for a few clarifications (so I know when to file a bug and when not, and how to package) about the different parts of the digikam-2 SC: * libkface, libkmap: Are these libraries "future parts of kdegraphics", i.e. will they be part of kdegraphics-4.7? * libkipi, libkexiv2, libkdcraw: Are these library versions "prereleases" of kdegraphics-4.7, and can we safely assume that the API remains stable? * kipi-plugins: Is this release _supposed to build_ with kde-4.6.0 versions of libkipi, libkexiv2, libkdcraw? * core/digikam: Is this release _supposed to build_ with kde-4.6.0 versions of libkipi, libkexiv2, libkdcraw? Especially the last two parts are pretty high on my personal wish list; while adding new libraries to an existing installation is easily done, replacing existing kde components is frowned upon heavily by our QA... TIA, Andreas
For additional information: * digikam core and kipi-plugins 2.0.0-beta2 compile and run fine with libkipi and libkexiv2 from kde-4.6.0 * kipi-plugins compiles fine with libkdcraw from kde-4.6.0 * digikam core build fails with libkdcraw from kde-4.6.0, see bug 265328 If this one problem can be fixed, we from Gentoo should be happy. (libkface and libkmap will just be declared as new external libraries then.)
Ping... KDE 4.7beta1 is approaching. * Are there differences (other than minor bugfixes etc) between the libraries in digikam 2.0.0beta5 and KDE 4.7beta1? Will Digikam core (be intended to) build against KDE 4.7? * Are any of the new libraries moving into KDE? (i.e. libkmap, libkface, libmediawiki)
Andreas, as KDE 4.7 is out since few month, i think you find a response of your questions. Right ? Gilles Caulier
Sure... sorry I completely forgot about this bug. It all builds fine with any kde-4.7. Please tell us when you intend to switch to 4.8 though... :)