[Kde-imaging] ksaneplugin (and libksane)

Aaron J. Seigo aseigo at kde.org
Fri May 9 06:18:28 CEST 2008


On Thursday 08 May 2008, Aurélien Gâteau wrote:
> With this in mind, maybe we could consider moving kipi-plugins to
> extragear/graphics.

agreed.

> This would allow compiling everything using the following order:
> 1. extragear/libs
> 2. kdegraphics
>     because gwenview depends on extragear/libs/libkipi
> 3. extragear/graphics
>     because kipi-plugins/acquireimages depends on kdegraphics/libksane

for the time being i think this would be fine.

> 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.

if no other apps in kde's main modules other than kdegraphics uses those libs, 
introducing a libs module is just adding more complexity to the equation?

i dunno; i'd like to see libkipi move into kdegraphics at some point, such as 
when the kde4 port is stable.

> This would give the following compilation order:
> 1. extragear/libs | kdegraphicslibs (order is not relevant)
> 2. kdegraphics | extragear/graphics (order is not relevant)

or:

0. kdegraphics
1. extragear/graphics

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20080508/a5268c6a/attachment.pgp 


More information about the Kde-imaging mailing list