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

Achim Bohnet ach-guest@costa.debian.org
Thu, 24 Mar 2005 22:45:34 +0000


Author: ach-guest
Date: 2005-03-24 22:45:33 +0000 (Thu, 24 Mar 2005)
New Revision: 920

Modified:
   kde-extras/digikam/trunk/debian/TODO
Log:
Sync with changes I had on my disk.



Modified: kde-extras/digikam/trunk/debian/TODO
===================================================================
--- kde-extras/digikam/trunk/debian/TODO	2005-03-24 20:51:48 UTC (rev 919)
+++ kde-extras/digikam/trunk/debian/TODO	2005-03-24 22:45:33 UTC (rev 920)
@@ -1,14 +1,26 @@
-Nice to have:
+Nice to have
+------------
 
 o add .xpm add file for debian menu file.
 
-o digikam.desktop  is not freedesktop app desktop file.
-	f.d.o desktop files are converted by pkg menu-xdg to debian menu
-	compatible files: http://bugs.kde.org/show_bug.cgi?id=98466 and
-	#271562
+o digikam.desktop is not a freedesktop app desktop file.
+	o See #271562 and http://bugs.kde.org/show_bug.cgi?id=98466
+	o check menu-xdg if menu file is still needed when desktop file
+	  is converted
 
-o (low prio) check sqlite mods of in tree source against sqlite in Debian
+o check what can be done to make setup of hotplug easier.
+	a) gphoto2 cameras -> Joergs (?) digikam-hotplug script
+	b) mass storage cameras
 
+Low priority stuff
+------------------
+
+o split into digikam and libdigikam0-dev.  (lintian complains)
+	--> no need as long as digikamimageplugin is the only external
+	user and upstream release digikam{,imageplugins} always together.
+o check sqlite mods of in tree source against sqlite in Debian
+	(ask Renchi if the last sqlite DSA are incorporated)
+
 	[18:57] <allee> pahli_bar: duplicate included code, possible future security fixes ...
 	[18:57] <pahli_bar> allee: the problem is default sqlite included with most distros doesn't have a) thread support b) utf8 support compiled in
 	[18:58] <allee> pahli_bar: well and not seeing this frighting warings during compile is a bonus too ;)
@@ -37,8 +49,4 @@
 	[22:52] <pahli_bar> though i don't recommend it. but its your call
 	[22:52] <allee> no I stick with upstream ;)  Following another source is not easier that stick with what you do
 
-o split into digikam and libdigikam0-dev ??????
-	--> no need as long as digikamimageplugin is the only external
-	    user and upstream will release digikam{,imageplugins}
-	    together in case of ABI changes.