1 Towards replacing rpm + yum (0.1):
5 - rpm file parser, create repo command
9 - versions in depsolving
13 - merge file lists when merging package sets
15 - import filelist.xml.gz too in yum importer
19 - figure out how to canonically represent empty string... ~0?
23 - eliminate duplicate entries in package property lists.
25 - keep history of installed packages/journal of package transaction,
26 so we can roll back to yesterday, or see what got installed in the
29 - gzip repository of look-aside pkg xml files somehow?
31 - transactions, proper recovery, make sure we don't poop our package
32 database (no more rm /var/lib/rpm/__cache*).
34 - rewrite qsort and bsearch that doesn't require global context var
35 and can output a map describing the permutaion.
37 - use hash table for package and property lists so we only store
38 unique lists (like for string pool).
40 - use existing, running system as repo; eg
42 razor update razor://other-box.local evince
44 to pull eg the latest evince and dependencies from another box. We
45 should be able to regenerate a rzr pkg from the system so we can
46 reuse the signature from the originating repo.
48 - Ok, maybe the fastest package set merge method in the end is to use
49 the razor_importer, but use a hash table for the properties. This
50 way we can assign them unique IDs immediately (like tokenizing
53 - test suite should be easy, just keep .repo files around and test
54 different type of upgrades that way (obsoletes, conflicts, file
55 conflicts, file/dir problems etc). Or maybe just keep a simple file
56 format ad use a custom importer to create the .repo files.
58 - pipelined download and install; download is network bound, install
59 is disk bound. Start installing once we have self-contained set of
60 packages. Install in reverse topo-sort order. Interruptible
61 installation; stops at nearest checkpoint.
63 - split out hash table code from importer, make the merger use just
68 do { ... } while (((e++)->name & RAZOR_ENTRY_LAST) == 0);
70 idiom for iteration of directories.
72 - version the sections in the file, put the element size in the header
73 so we can add stuff to elements in a backwards compatible way.
75 - overlay package sets? mount a read-only /usr over nfs or from the
76 virt-host and have a local package set overlaid over the read-only
77 one. shouldn't need new features in the core package set data
78 structure, but should be just conventions on top. we have the base
79 package set from the r/o system, the overlay set from the local
80 system and we can have an effective package set which is the merge
81 of everything from the overlay into the base set. the effective set
82 is easy to compute and we could do it on the fly or cache it. or
83 maybe the effective set is the on-disk representation and the
84 overlay can be computed when needed, we just keep a link back to the