summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@redhat.com>2007-10-25 13:25:45 -0400
committerKristian Høgsberg <krh@redhat.com>2007-10-25 23:31:09 -0400
commitce94cdd024e95183da678d4dceb829bb8e378c49 (patch)
tree2cc1b2a64e5e3b0733afb4614429529f410dab70 /TODO
parentf4eda2807e7b743930c047bd76afcc371b5ce815 (diff)
More ideas for TODO.
Diffstat (limited to 'TODO')
-rw-r--r--TODO15
1 files changed, 15 insertions, 0 deletions
diff --git a/TODO b/TODO
index eea05b0..39f5781 100644
--- a/TODO
+++ b/TODO
@@ -53,3 +53,18 @@
do { ... } while (((e++)->name & RAZOR_ENTRY_LAST) == 0);
idiom for iteration of directories.
+
+- version the sections in the file, put the element size in the header
+ so we can add stuff to elements in a backwards compatible way.
+
+- overlay package sets? mount a read-only /usr over nfs or from the
+ virt-host and have a local package set overlaid over the read-only
+ one. shouldn't need new features in the core package set data
+ structure, but should be just conventions on top. we have the base
+ package set from the r/o system, the overlay set from the local
+ system and we can have an effective package set which is the merge
+ of everything from the overlay into the base set. the effective set
+ is easy to compute and we could do it on the fly or cache it. or
+ maybe the effective set is the on-disk representation and the
+ overlay can be computed when needed, we just keep a link back to the
+ base.