> > how does history(1) work in the face of a complicated namespace? > > we get buy now because the rules are pretty simple. if you want to > > find how the modifications to /386/lib/libc.a, you know where that > > is. if you bind 100 packages on top of /386/lib, it becomes necessary > > to deconstruct namespaces continually. the abstraction of namespace > > starts to break down. > > > > this also breaks plumbing while debugging with acid unless quirky > namespace is global, but then if it's global why do you need the binds!
in order for a namespace to be non-empty, it will need binds or mounts somewhere. even a "global" (i'm assuming by global you mean in /lib/namespace) bind will not work well with history. since the namespace isn't fancy enough to do rewriting based on pattern matching. (thank god!). i suppose you could write a script, but such a script would need to generate a set of binds for each day of the dump. are you ready for a 350*(1 + 2136) line namespace? - erik
