<br><br><div class="gmail_quote">2008/10/29 Angelo Naselli <span dir="ltr"><<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
marted́ 28 ottobre 2008 alle 21:09, Colin Guthrie ha scritto:<br>
<div class="Ih2E3d">> There is definitely (IMO) scope for rebasing the whole KIPI API on top<br>
> of Akonadi but this is perhaps something that is best left for a future<br>
> occasion. Perhaps not, as I know the API breakage is up for discussion,<br>
> but I don't want to bite of more than can be comfortably chewed at the<br>
> moment!<br>
><br>
</div>There's no big problems in breaking on trunk, untill kde 4.2 freeze time.<br>
The discussion about api/abi breakage i'd like to have during kde code<br>
sprint concerns on the stable branch and during beta/rc phase, having<br>
attention to stable distros, e.g. the ones who want to use our packages.<br>
<br>
I mean i don't like to think we have to implement every time new<br>
functionalities during beta/rc, i'd expect more to stabilize the code instead.<br>
Moreover we can't base our work always on trunk, as far as our final product<br>
concerns. Maybe I'm wrong, but i can see the mess digikam does on mandriva<br>
2009.0. </blockquote><div><br>as i have already said, digiKam 0.10.0 is currently in beta release and not stable. it's stupid to include it in Mandriva as official and stable version because it must not be used in production. I specify this point in release announce.<br>
<br>We have released a stable version for KDE3 : <a href="http://0.9.4.">0.9.4.</a> this one must be used in production. I don't know why Mandriva force use to use unstable version of program, especially with digiKam. KDe3 version can be used without problem under KDE4. There are some others KDE3 programs installed in Mandriva 2009.0 under KDE4 desktop as K3b or konversation. Why not digiKam ?<br>
<br>Also, if you want to unbreak binary compatibility with current kdegraphics/libs installed by default from KDE 4.1.2 under Mandriva and use digiKam from trunk using kdegraphics/libs from trunk, just install these component un a dedicated place as /usr/local, and pass this path to digiKam cmake configuration...<br>
<br>Best<br><br>Gilles Caulier<br><br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It is almost unusable and to get new betas we need to backport<br>
things from kdegraphics trunk, that's ok for developers not for final users.<br>
So more attention to stable distros should be taken IMHO.<br>
I don't mean we don't have to add new features of course, but maybe we<br>
should work on branches once we have a beta out, and going on trunk for<br>
future releases. Of course it's a nonsense (always imo) releasing a new stable<br>
based on kdegraphics trunk since it has not been released yet....<br>
<br>
My 2€ cents.<br>
<font color="#888888"> Angelo<br>
<br>
</font><br>_______________________________________________<br>
Kde-imaging mailing list<br>
<a href="mailto:Kde-imaging@kde.org">Kde-imaging@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-imaging" target="_blank">https://mail.kde.org/mailman/listinfo/kde-imaging</a><br>
<br></blockquote></div><br>