Add a note about section handling in search_contents

[deb/packages.git] / TODO

diff --git a/TODO b/TODO
index c3602007d4c46ca0655210f0d65cfa72b201832c..c92524c6f2171bbbe70eadba240335002fbba2b3 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-search_packages.pl:
+search_packages:
 - all searches:
   - Display "$pkg ($section) shortdesc from stable (or if not available, testing, unstable, ...)"
     tersely on one line each, with "#foo" links to what's currently displayed.
@@ -10,8 +10,6 @@ search_packages.pl:
        course) the search term
 - exact package searches
 - substring searches on packages:
-  - don't do exact lookups, but use '^' prefix token
-  - only do for >= 2 characters
   - don't allow whitespace in it, warn when people use common wildcards like
        *, ?, ^, $ (not possible)
   - When overflow, iterate the first couple of packages that *start* with the
@@ -25,7 +23,44 @@ search_packages.pl:
   - Better exact=1 performance by indexing per word?
   - drop case-sensitive from options, descriptions.txt all lowercase and without
        punctuation, such that instead of =~ //, indexof can be used
+  - in results, show full descriptions, so one sees what's being matched?
+
+- backend:
+  - Ensure that in _small.db, newest version for each suite is first,
+       show_package relies on that. So foreach suite, 'newest entry', and only
+       then, all the other entries
+
+search_contents:
+- regain section (main/contrib/non-free) information? It is currently
+   not available at all.
+
+Static pages:
+- try to make it faster
 
 General:
 - Try to break everything with empty/short searches
 - Check for case sensitive consistency
+- Fix assumption that archive doesn't show up in any url, consistency-fy
+  dealing with archives of a different set than (us, non-us, security)
+- grep -ri fixme
+- searchon=all -> searchon=descriptions?
+- quicksearch box: copy parameters of current search (exact,suite,arch,etc),
+  or rather, always use defaults? Both have their pro&cons... former is more
+  obscure, but otoh, for typo fixing more appropriate.
+  Maybe best of both worlds is 'modify search' below results, where you can
+  generalize/specificy arch, etc etc?
+- In Search.pm, make sure read_entry_small only scans a bit, and not all --
+  once you have #max_nr_of_suites, you know you won't find the queried suite
+  anymore, so search further is futile. Maybe the backend could even add a
+  marker, ignored by read_entry_all, but understood by read_entry_small, that
+  indicates end of $res2 and start of $res3
+- Debtags: print friendly names instead of raw names?
+- Store in db \1-separated, and split on that, instead of the more fragile
+  '/, /' split
+
+
+Missing pieces from old code:
+ - DDTP support (but without a working DDTP I will not invest any time
+   in that)
+ - search_packages compatibility (we should at least ensure we don't break
+   sarge's reportbug)