| value: \0 separated tuples of "archive suite arch component section priority version shortdescription"
| (so you can split on spaces in 8 pieces, but need to not split further
| because shortdescription can have spaces)
-| arch can also be 'virtual', with c/s/p/v being undefined then, and
-| shortdescription being a space-separated list of packages providing
-| the package that is the key
Notes: - maybe add did right before shortdescription?
- - TODO: make sure for each (archive,suite), newest package is shown
- first, and all newest versions for each such section is first, so
- that one can efficiently lookup just the newest entry for a given
- (archive,suite)
+ - for each suite, newest package is shown first, and (suite,
+ architecture) is unique, the newest one is choosen. Once you find
+ the right suite, you know you've got the newest, once you found
+ your (suite,arch), you know you've found the only unique such entry
+ - The very first element is different (TODO: maybe should be
+ different DB then?), a \01 separated hash of suite -> provided-by,
+ like "suite1\01prov1 prov2\01suite2\01prov1"
| package_postfixes.db:
| key: a postfix string of a package name