[Digikam-devel] Fwd: [Kde-imaging] Re: Re: Git migration for 2.0.0 + code components re-structuring...

Gilles Caulier caulier.gilles at gmail.com
Thu Dec 9 17:18:49 GMT 2010

---------- Forwarded message ----------
From: Angelo Naselli <anaselli at linux.it>
Date: 2010/12/9
Subject: [Kde-imaging] Re: [Digikam-devel] Re: Git migration for 2.0.0
+ code components re-structuring...
To: kde-imaging at kde.org

giovedì 9 dicembre 2010 alle 15:49, Gilles Caulier ha scritto:
> I know that Mandriva backport trunk/unstable but it's not the case of
> debian ubuntu, and fedora, which won't to do work in this way. They
> want to backport unstabilized code in all case. It's a logic goal...
bah, logic? what's logic in having an unstable system if you're not e tester?
I don't mean digikam is unstable, and anyway if someone wants to have
last release
of all in his distribution can always backports all he needs.
I don't talk about mandriva, i just talk about a way of thinking (mine
of course ;)).

>Why not to try a digiKam package as explained before, without to fork
>unstable libkexiv2, libkdcraw for the moment ? We can see if it's
We can move every libkxxx we need, but if we share one of them with
someoneelse (kdegraphics for instance) we must take that in account.
We cannot do what we want and we have to decide if depending on trunk
("unstable") or branch (should be stable).

Anyway deciding to move libkxxx from kdegraphics to digikam (or extragear,or...)
should be decided also with all that projects that need them...

Just my 2 €cents

Kde-imaging mailing list
Kde-imaging at kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20101209/d9112498/attachment.sig>

More information about the Digikam-devel mailing list