More ideas for TODO.
1.1 --- a/TODO Thu Oct 25 13:21:26 2007 -0400
1.2 +++ b/TODO Thu Oct 25 23:31:09 2007 -0400
1.3 @@ -53,3 +53,18 @@
1.4 do { ... } while (((e++)->name & RAZOR_ENTRY_LAST) == 0);
1.5
1.6 idiom for iteration of directories.
1.7 +
1.8 +- version the sections in the file, put the element size in the header
1.9 + so we can add stuff to elements in a backwards compatible way.
1.10 +
1.11 +- overlay package sets? mount a read-only /usr over nfs or from the
1.12 + virt-host and have a local package set overlaid over the read-only
1.13 + one. shouldn't need new features in the core package set data
1.14 + structure, but should be just conventions on top. we have the base
1.15 + package set from the r/o system, the overlay set from the local
1.16 + system and we can have an effective package set which is the merge
1.17 + of everything from the overlay into the base set. the effective set
1.18 + is easy to compute and we could do it on the fly or cache it. or
1.19 + maybe the effective set is the on-disk representation and the
1.20 + overlay can be computed when needed, we just keep a link back to the
1.21 + base.