[Kde-imaging] libkipi and libksane to kdegraphics?

[Gilles Caulier]

2008/5/4 Angelo Naselli <anaselli at linux.it>:
> domenica 04 maggio 2008, Kåre Särs ha scritto:
>  > Hi,
>
> Hi
>  >
>  > When I was about to move libksane to kdegraphics I noticed that Gwenview
>  > depends on libkipi from extragear-libs.
>  gwenview does not depend on libkipi, it just builds with
>  kipi support to use kipi-plugins if libkipi is present.
>
> > This prevents the moving of libksane
>  > to kdegraphics since kipi-plugins (separate, but also part of extragear-libs)
>  > depends on libksane.
>  the problem here i believe is that libksane needs libkipi, while gwenview can
>  build without.
>
>
>  > The solution I would prefere would be that libkipi also would move to
>  > kdegraphics. The other would be that libksane remains in extragear-libs.
>

no. there is no plan to follow KDE release with libkipi especially with KDE4.x

digiKam and kipi-plugins use libkipi without conditional compilation
rules. both are in extragear. This need to still homogenous.

>  Well we could think about that, since libkipi hasn't changed since ages
>  in kde3, but unfortunately I'm not sure if that is a good solution for us
>  since we're not so many to take a fixed developing plan.
>

Like gwenview is in kde-graphics and can use libkipi from
extragear-libs without problem (if it needs), i propose to not move
libksane in kde-graphics. by this way you can move skanlite to
kde-graphics and use libksane as well, like gwenview.

Or perhaps are you more ambitious plan for libksane, like to replace
libkscan as well (with Win32 and MacOSX support as well). In this
case, yes, it will be better to move libksane also to kde-graphics.

Best

Gilles