|
From: Laszlo K. <las...@su...> - 2000-11-22 10:21:36
|
> The current way things are designed is that it will have one contents list > for the system. Of course you can always create another one somewhere > else using the -p flag, but generally they would contain the same > information and only the default one will get updated each time a document > is installed. By specifying which OMF directories you want to include, > these databases could be made to differ. We don't currently have a > mechanism for supporting or specifying multiple OMF directories, but that > would be fairly straightforward and is planned. This will make it very > simple for users to have their own local databases which vary from the > system's database by having OMF files in, say, $HOME/.scrollkeeper/omf > which add to or over-ride the system defaults. We will have to think this through. The current implementation does not comply with the layering of information and configuration on the system (network-wide, system-wide, user). I'll look into this in more detail later and see what I can come up with. I don't know how well Linux complies with this, Solaris does it very well in general. I'll check how they do it with documentation. This is an architectural issue, it is very important to sort it out before we go too deep in development. Laszlo |