3 - Display "$pkg ($section) shortdesc from stable (or if not available, testing, unstable, ...)"
4 tersely on one line each, with "#foo" links to what's currently displayed.
5 - The 'extended' can maybe also have full descriptions then (maybe add did
7 - Unify exact & subword -- reduce naming confusion with 'exact' meaning
8 either "exactly the same" or "full word"
9 - When doing substring searches, hilight with html backgroup color (css of
10 course) the search term
11 - exact package searches
12 - substring searches on packages:
13 - don't allow whitespace in it, warn when people use common wildcards like
14 *, ?, ^, $ (not possible)
15 - When overflow, iterate the first couple of packages that *start* with the
16 substring, if any? Maybe list those first, and only then real substring
18 - In db, add "abc: too many matches" to postfixes when there's a "abcd: 90
19 matches" and abce: 90 matches"
23 - Better exact=1 performance by indexing per word?
24 - drop case-sensitive from options, descriptions.txt all lowercase and without
25 punctuation, such that instead of =~ //, indexof can be used
26 - in results, show full descriptions, so one sees what's being matched?
29 - Ensure that in _small.db, newest version for each suite is first,
30 show_package relies on that. So foreach suite, 'newest entry', and only
31 then, all the other entries
34 - with this design, we can resolve experimental dependencies from unstable
35 - try to make it faster
38 - Try to break everything with empty/short searches
39 - Check for case sensitive consistency
40 - Fix assumption that archive doesn't show up in any url, consistency-fy
41 dealing with archives of a different set than (us, non-us, security)
42 - Some packages are both concrete and virtual, deal with that: in depends
43 display of show_package (now if a package is concrete, you only see that),
44 and eh, somewhere else too ttbomk
46 - searchon=all -> searchon=descriptions?
47 - quicksearch box: copy parameters of current search (exact,suite,arch,etc),
48 or rather, always use defaults? Both have their pro&cons... former is more
49 obscure, but otoh, for typo fixing more appropriate.
50 Maybe best of both worlds is 'modify search' below results, where you can
51 generalize/specificy arch, etc etc?
52 - In Search.pm, make sure read_entry_small only scans a bit, and not all --
53 once you have #max_nr_of_suites, you know you won't find the queried suite
54 anymore, so search further is futile. Maybe the backend could even add a
55 marker, ignored by read_entry_all, but understood by read_entry_small, that
56 indicates end of $res2 and start of $res3
60 - amd64 security is getting displayed weirdly
61 - kfreebsd-i386 contents files have no header and aren't read correctly
64 Missing pieces from old code:
67 - DDTP support (but without a working DDTP I will not invest any time
69 - search_packages compatibility (we should at least ensure we don't break