tersely on one line each, with "#foo" links to what's currently displayed.
- The 'extended' can maybe also have full descriptions then (maybe add did
to _small.db?)
+ - Unify exact & subword -- reduce naming confusion with 'exact' meaning
+ either "exactly the same" or "full word"
+ - When doing substring searches, hilight with html backgroup color (css of
+ 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
- fulltext search:
- Max 100 results
- 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
+
+- 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
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)
+- Some packages are both concrete and virtual, deal with that: in depends
+ display of show_package (now if a package is concrete, you only see that),
+ and eh, somewhere else too ttbomk
+- 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?
+
+
+Bugs:
+- amd64 security is getting displayed weirdly
projects / deb / packages.git / blobdiff