From kde-core-devel Fri Jan 30 10:31:53 2015 From: Gilles Caulier Date: Fri, 30 Jan 2015 10:31:53 +0000 To: kde-core-devel Subject: Re: libkgeomap Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=142261396427763 2015-01-30 11:18 GMT+01:00 Pino Toscano : > On Friday 30 January 2015 09:16:47 Raymond Wooninck wrote: >> But as that >> Digikam is moving more and more to a Qt5 application, then a Frameworks based >> one I wonder if the maintainers will go for this separation. > > I don't see how things will change because of this. Currently, the > kdegraphics libraries (libkipi, libkexiv2, libdcraw, and recently also > libkface) have regular release together with KDE SC/whatever; however, > they are bundled (as snapshots from git/master, even) in the digikam > release tarball as well, and possibly digikam even requires (it did a > couple of times in the past) functions added only to master in those > libraries, and not available in their last stable series. False. libs are bundled in tarball, but not used at compilation time (look cmake options in SC repository). > > In short: maintainers should simply stop bundling libraries together > with digikam, and just make sure digikam (and kipi-plugins as well) > builds and work fine at least with the latest stable series of them. > > Back to the topic of this thread: I'd mildly oppose to move libkgeomap > to kdegraphics, since: > a) its API and ABI get broken from time to time (even too often), with > no actual bump of SONAME false. Look API and ABI history in top of lead cmake scripts for each projects... > b) digikam people rarely care about non-master branches of those > libraries, fixing bugs in master only and leaving stable series > without fixes (and distros usually have to backport those on their > own) false. When it's possible we do it, when time permit. > c) there is simply nothing that prevents something in extragear/libs > to have own releases (and actually, that's exactly what extragear > is for), and to be used by other applications This join my older viewpoint (5/6 years ago) to NOT share libkipi, libkdcraw, libkexiv2, etc with the rest of the world because it will be amount to work to solve problems due to sharing rules. I remember peoples from KDE who ask to changes my viewpoint... We have tried to do the best, and as i can see it's never enough... Gilles Caulier