<br><br><div class="gmail_quote">On Thu, Dec 9, 2010 at 5:01 PM, Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Martin,<br>
<br>
this is exactly the purpose of my proposal, to create a digiKam<br>
package including kipi-plugins and shared libs.<br>
<br>
If the concept is fine, we can plan to host by the same way a forked<br>
version of libkexiv2 and libkdcraw. For the moment it's not the goal.<br>
We can life a little bits with kdegraphics/libs.<br></blockquote><div><br></div><div>With git we can use git hooks , these are small shell scripts which get executed </div><div>based on some git event . eg. before git-push , after git-rebase etc.</div>
<div><br></div><div>We can pull in from the different places using a hook, that</div><div>should abstract some of the (pulling from different places)</div><div>and also prevent forking.</div><div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://www.kernel.org/pub/software/scm/git/docs/githooks.html">http://www.kernel.org/pub/software/scm/git/docs/githooks.html</a></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Only one library cannot not be shared like this : libkipi. Why?<br>
because this one is shared with Kphotoalbum and gwenview.<br>
<br>
Gilles<br>
<br>
2010/12/9 Martin Klapetek <<a href="mailto:martin.klapetek@gmail.com">martin.klapetek@gmail.com</a>>:<br>
<div class="im">><br>
> On Thu, Dec 9, 2010 at 10:34, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>><br>
> wrote:<br>
>><br>
>> About libkface, libkmap, it will work as kipi-plugins : it stand alone<br>
>> shared librared installed on the system.<br>
>><br>
>> This will solve the huge puzzle for us, digiKam & co developpers. As<br>
>> we maintain this code...<br>
>><br>
>> What do you think about ?<br>
><br>
> I agree to ship as many things as possible ourselves, or make them otherwise<br>
> independent. Because then distro packagers have problems packaging it and<br>
> users then end up with 1.2.0 in some recent distro and they are reporting<br>
> bugs against 1.2.0 and we just reply to update to newer version and try<br>
> again, but they actually can't, because thier distro doesn't package newer<br>
</div>Thi sis > version, because of the libs being part of KDE trunk (and<br>
<div class="im">they don't package<br>
> trunk stuff). So for the sake of the users, I think we should ship as many<br>
> things as possible ourselves.<br>
> Marty<br>
><br>
>><br>
>> Gilles Caulier<br>
>> _______________________________________________<br>
>> Digikam-devel mailing list<br>
>> <a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> Digikam-devel mailing list<br>
> <a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
><br>
><br>
</div>_______________________________________________<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>
</blockquote></div><br><br clear="all"><br>-- <br>regards<br>-------<br>Kunal Ghosh<br>Dept of Computer Sc. & Engineering.<br>Sir MVIT<br>Bangalore,India<br><br>Blog:<a href="http://kunalghosh.wordpress.com">kunalghosh.wordpress.com</a><br>
Website:<a href="http://www.kunalghosh.net46.net">www.kunalghosh.net46.net</a><br><br><br>