-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.
matches" and abce: 90 matches"
- 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
- in results, show full descriptions, so one sees what's being matched?
- backend:
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
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
+- Store in db \1-separated, and split on that, instead of the more fragile
+ '/, /' split
+- Fields we don't handle in any way currently:
+ Conflicts
+ Replaces
+ Enhances
+ Origin -- not needed
+ Bugs -- not needed
+ Task
+ Python-Version(s) -- not needed
+Cron:
+- Verify Release files
+- refactorize 100syncarchive* so that there is not so much copied code
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)
+ - search_packages result parser?
+ reportbug in sarge is completly broken in this regard anyway AFAICT
+ reportbug in etch works as long as there is the exact hit but
+ breaks once there is more than one hit