Switch debian build system to dh

[onak.git] / TODO

diff --git a/TODO b/TODO
index b282e9c1a4cec420321bdb39594f2945d4aaf25b..90d426a3319c4b2bebb6598b0556b16a7ada3c4c 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,28 +1,24 @@
-* Revoked keys on index.

 * Check keys on import?
 * Check keys on import?

-* config file
-* Sort out merging (use onak + some Perl to answer incoming email. Not
-  sure about keys via hkp yet though - need to send updates out).
+   * Non self-signed user IDs
+   * Non self-signed subkeys
+   * Invalid revocations
+   * Signatures marked as non-exportable
+   * PKS subkey damage

 * Better signature subpacket parsing (primary UID for example).
 * Better merging of signatures; need to compare subpackets on Type 4 packets
   and choose which we should use (how? most recent date?)
 * Honor no-modify keyserver flag ("Brian M. Carlson" <karlsson@hal-pc.org>)
 * Better txt2html routine.
 * Better signature subpacket parsing (primary UID for example).
 * Better merging of signatures; need to compare subpackets on Type 4 packets
   and choose which we should use (how? most recent date?)
 * Honor no-modify keyserver flag ("Brian M. Carlson" <karlsson@hal-pc.org>)
 * Better txt2html routine.

-* Remove bithelp.h (i386 only at present & inlined).
-  - Build and test on non-i386.
-* Pathfinder - graphical as well? Multiple paths?
+* Pathfinder - graphical as well?

 * Do pathlengths for similar email addresses to help aide keysigning.
   (ie "Find me the keys furthest from mine that end ox.ac.uk'")
   Suggested by Jochen Voss <voss@mathematik.uni-kl.de>.
 * Do pathlengths for similar email addresses to help aide keysigning.
   (ie "Find me the keys furthest from mine that end ox.ac.uk'")
   Suggested by Jochen Voss <voss@mathematik.uni-kl.de>.

-* Other stats. sixdegrees? with piccy? most signed? signs most?
+* Other stats. most signed? signs most?

 * DB access modules as a library to allow runtime configuration of it?
 * Clean up gcc warnings (`ll' length modifier especially! Also inline & wrong
   signedness for lo_read/write)
 * Test library?
 * DB access modules as a library to allow runtime configuration of it?
 * Clean up gcc warnings (`ll' length modifier especially! Also inline & wrong
   signedness for lo_read/write)
 * Test library?

-* autoconf
-* logging framework so we can log debug/warning messages and so on. syslog?
-* Check freeing.
+* Full email interface support (ADD, INDEX etc)

 * More comments.
 * Look at db2 backend - is it db2's fault? (Well, deadlock in that the library
 * More comments.
 * Look at db2 backend - is it db2's fault? (Well, deadlock in that the library

-  probably is...). Is there an alternative library that would provide us with
-  similar features but be more reliable? gdbm? Jason Harris suggests db3/4.
+  probably is...). Pull some of the DB3 stuff across for completeness.