[Kde-imaging] ksaneplugin (and libksane)

[Angelo Naselli]

> > well i do hope Aurelién will tell us his opinion, since we have
> > tlaked about that yesterday :)
> 
> Hehe, here I am, always late :)
Better than never :p

> With this in mind, maybe we could consider moving kipi-plugins to 
> extragear/graphics. We would have something like this:
> 
> extragear/
>    libs/
>      libkipi
>      libkexiv2
>      ...
>    graphics/
>      kipi-plugins/
>        acquireimages
>        ...
> 
> kdegraphics/
>    libksane
>    gwenview
> 
Well that could be ok, i've always wondered why kipi-plugins were under libs
since it's not a library :)
If Gilles agrees we can move to graphics. From kipi-plugins point of view should
need some cmake reworks but that should not be hard to, i believe. 
from digikam point of view extragears/libs is needed first as before, the only exception
is digikam, but since they are into graphics they can be used as it was for digikam-plugins 
in past, i believe

> The thing is: kdegraphics would still be both a library provider and 
> user. I think it would make sense to create a kdegraphicslibs package 
> which would contain libksane for now and would be a place for libkipi 
> if/when it's ready to move to the core of KDE.
> 
> This would give the following compilation order:
> 1. extragear/libs | kdegraphicslibs (order is not relevant)
> 2. kdegraphics | extragear/graphics (order is not relevant)
And that explains why i've talked about a kdegraphics-lib :)

Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20080509/9a218e3e/attachment.pgp