[EMAIL PROTECTED] (Marco Budde) writes: > Am 09.08.98 schrieb apharris # burrito.onshore.com ... > APH> It assumes that (a) files are .dhelp files, (which is wrong), (b) > APH> metadata is installed under /usr/doc (which is not required, and also > > Of course it#s required.
Nope. > APH> wrong, i.e., the local sysadmin should be able to maintain metadata > APH> under /usr/local or /opt or whatever they feel like), and (c) that > > This is not possible with the /var solution. And at the moment I#m talking > only about the Debian documentation. You shouldn't be. > APH> metadata files are immediately recognizable by their filename, which > APH> is currently not required, > > ??? .docreg has to be part of the filename. Nope. > APH> and (d) all recognizable docreg files are > APH> meant to bbe installed (say, running 'locate .docreg' might turn up > APH> files, say checked out copies from a cvs repository; obviously > APH> checking in all files turned up by 'locate .docreg' would be > APH> non-robust). > > That#s right. At this problem will be fixed by your doc-base system :). > You have mentioned that you will store the the filenames of the installed > docreg files. Right? Yes sir! > That your package could offer a -r option. If the user users this option, > your program could call a registered dhelp script. This script will use > option -a of dhelp to add all registered .docreg files to a new db. Is > that ok? Yes sir! > APH> My solution is, as I said, to maintain a list of installed docreg > APH> files in /var/state/metadata/docreg_files . What maintains the list? > > Great. Excellent! ;) Now there's just the problem of install-docs calls being made before install-docs is installed, and how to deal with that. Any suggestions? -- .....A. P. [EMAIL PROTECTED]<URL:http://www.onShore.com/>
