[Pkg-kde-commits] rev 1737 - kde-extras/digikam/trunk/debian

Achim Bohnet ach-guest at costa.debian.org
Wed Sep 7 20:04:37 UTC 2005


Author: ach-guest
Date: 2005-09-07 20:04:36 +0000 (Wed, 07 Sep 2005)
New Revision: 1737

Modified:
   kde-extras/digikam/trunk/debian/TODO
Log:
fix my memory leak


Modified: kde-extras/digikam/trunk/debian/TODO
===================================================================
--- kde-extras/digikam/trunk/debian/TODO	2005-09-07 20:00:03 UTC (rev 1736)
+++ kde-extras/digikam/trunk/debian/TODO	2005-09-07 20:04:36 UTC (rev 1737)
@@ -25,6 +25,38 @@
 	a) gphoto2 cameras -> Joergs (?) digikam-hotplug script
 	b) mass storage cameras
 
+o relibtoolize digikam & co:
+
+
+	[20:58] <dato> allee: ping was to suggest you relibtoolizing digikam and related packages, in order to loose some dependencies.
+	[20:58] <dato> not that it matters _much_, but it may save you being removed from testing next time there is a big transition ongoing, as has happened now. :)
+	[20:59] <allee> heh heh ;)
+	[21:00] <allee> what do you mean with relibtoolizing excactly.  More than updating auto* and rebuilding?
+	[21:00] <dato> what do you mean with "updating auto*"?
+	[21:00] <allee> I mean the usual make -f Makefile.cvs
+	[21:01] <allee> use latest version of auto* tools for run make -f Makefile.cvs
+	[21:01] <dato> then, relibtoolizing is like that, but using the latest version of libtool (and a small patch)
+	[21:02] <dato>         cp -f /usr/share/libtool/libtool.m4 $(DEB_SRCDIR)/admin/libtool.m4.in
+	[21:02] <dato>         cp -f /usr/share/libtool/ltmain.sh  $(DEB_SRCDIR)/admin/ltmain.sh
+	[21:03] <dato> and the patch can be found in branches/3.4/common-patches/something_undefined_bla.diff
+	[21:03] <dato> 07_disable_no_undefined.diff
+	[21:04] <allee> Ah, I also remember that someone of the team 'complained' about noone using 'qt-kde' infrastruction.  E.g. common-patches, etc ...
+	[21:04] [Notify] Thucydides is online (irc.de.freenode.net).
+	[21:05] <allee> is amarok or gwenview a good example how to use the infrastruckture (I like learning by example ;)
+	[21:06] <dato> allee: well, amarok runs make -f Makefile.cvs (or similar) at build-time; not everybody likes that.
+	[21:06] <dato> allee: as for common-patches, there's no warrantly they'd apply to your admin/ dir, they're for the admin version of the latest KDE (and your upstream may use an older one).
+
+o check pkg-qt-kde build infrastructure (common-patches and more?)
+
+	[21:04] <allee> Ah, I also remember that someone of the team 'complained' about noone using 'qt-kde' infrastruction.  E.g. common-patches, etc ...
+	[21:04] [Notify] Thucydides is online (irc.de.freenode.net).
+	[21:05] <allee> is amarok or gwenview a good example how to use the infrastruckture (I like learning by example ;)
+	[21:06] <dato> allee: well, amarok runs make -f Makefile.cvs (or similar) at build-time; not everybody likes that.
+	[21:06] <dato> allee: as for common-patches, there's no warrantly they'd apply to your admin/ dir, they're for the admin version of the latest KDE (and your upstream may use an older one).
+	[...]
+	[21:11] <dato> Thucydides: btw, when you have a minute, I'd like to comment on a weird problem I'm having
+	[21:11] <Thucydides> allee: gwenview is a good example. I use all the common-patches except the visibility one, since I don't need it and it doesn't apply.
+
 Low priority stuff
 ------------------
 




More information about the pkg-kde-commits mailing list