Using the KomparePart in KDevelop

[Kevin Kofler]

On Friday 24 July 2009, Andreas Pakulat wrote:
> BTW: I also plan to have a kdesdklibs module for KDE 4.4 because we need to
> share some code+data between kdevelop and kapptemplate (and Anne-Marie
> doesn't want to use kdevplatform for a simple app like kapptemplate).

I really don't see the benefit of yet another kde*libs package. Can't we just 
put that stuff into kdesdk? It's up to distributions to make a kdesdk-libs 
subpackage. In fact, we're already doing it in Fedora.

And a big problem is: the non-libs package will most likely end up including 
some libs anyway, e.g. kdepim does. So now, in Fedora, we have a kdepim-libs 
package (a subpackage of kdepim) and a kdepimlibs package (the upstream 
kdepimlibs). Perhaps unsurprisingly, that has already confused some users. And 
as I said, the current kdesdk also has some libs, so we could end up with the 
same mess there.

> So maybe we could think about moving the interface header to that module
> (once it exists), so KDevelop has only a runtime dependency on kdesdk and no
> (optional) compile-time dependency?

Having only runtime dependencies with no corresponding compile-time dependency 
helps basically nobody. Users who build the stuff themselves will need the 
runtime dependency anyway, and for binary distributions, one BuildRequires 
more or less for the build system to automatically fetch isn't going to matter 
at all. If you can save a runtime dependency, that can be interesting (but see 
the previous paragraphs!), otherwise it's just worthless.

        Kevin Kofler