[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: ksaneplugin (and libksane)
From: Michael Pyne <mpyne () purinchu ! net>
Date: 2008-05-04 22:53:46
Message-ID: 200805041853.52567.mpyne () purinchu ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sunday 04 May 2008, Kåre Särs wrote:
> Hi,
>
> I have now moved ksaneplugin to kdegraphics, but not libksane.
>
> I did not move libksane because of circular dependency problems:
> Gwenview -> libkipi (kipi-plugins) -> libksane
So basically acquireimages would depend on libksane (which we want to move
out of extragear) and moving it to kdegraphics would make that kipi plugin
depend on kdegraphics?
Looks like our options are to
1. Move libksane to kdelibs since multiple applications use it.
2. Make a new kdegraphicslib or similar and make extragear/libs/kipi-plugins
optionally depend on it and have kdegraphics depend on it.
3. Leave libksane in extragear/libs even though it is ready to be moved into
KDE and have kdegraphics optionally depend on it.
4. Move libksane to kdegraphics and make extragear/libs/kipi optionally
depend on it. This depends on stuff in kdegraphics not depending (even
optionally) on things in extragear/libs/kipi though, which Gwenview does.
I don't like option 3 because eventually some other library will be ready to
leave extragear and we'll likely have the same issue. Do we have a set
policy for how libraries migrate out of extragear, or just applications?
If don't like option 4 because of the circular dependencies involved. It's
just not a good idea to allow circular dependencies to exist.
If libksane is small enough I'd say use option 1, otherwise I'd say we need
to do option 2 (or something similar). Anyone have other thoughts?
Regards,
- Michael Pyne
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Consolas'; font-size:11pt; font-weight:400; \
font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">On Sunday \
04 May 2008, Kåre Särs wrote:</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> Hi,</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> I have now moved ksaneplugin to kdegraphics, but not \
libksane.</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> I did not move libksane \
because of circular dependency problems:</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> Gwenview -> libkipi (kipi-plugins) -> \
libksane</p> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">So basically acquireimages would depend on libksane (which we want \
to move out of extragear) and moving it to kdegraphics would make that kipi plugin \
depend on kdegraphics?</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">Looks like our options are to</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">1. Move libksane to kdelibs \
since multiple applications use it.</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">2. Make a new kdegraphicslib or similar and make \
extragear/libs/kipi-plugins optionally depend on it and have kdegraphics depend on \
it.</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">3. Leave \
libksane in extragear/libs even though it is ready to be moved into KDE and have \
kdegraphics optionally depend on it.</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">4. Move libksane to kdegraphics and make \
extragear/libs/kipi optionally depend on it. This depends on stuff in kdegraphics \
not depending (even optionally) on things in extragear/libs/kipi though, which \
Gwenview does.</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">I don't like option 3 because eventually some \
other library will be ready to leave extragear and we'll likely have the same issue. \
Do we have a set policy for how libraries migrate out of extragear, or just \
applications?</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">If don't like option 4 because of the circular \
dependencies involved. It's just not a good idea to allow circular dependencies to \
exist.</p> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">If libksane is small enough I'd say use option 1, otherwise I'd \
say we need to do option 2 (or something similar). Anyone have other thoughts?</p> \
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">Regards,</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"> - Michael Pyne</p></body></html>
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic