Re: [Scrollkeeper-devel] Registering documents with ScrollKeeper

[Nik C. <ni...@no...>]

On Tue, Nov 14, 2000 at 11:05:09AM -0600, Dan Mueth wrote:
> Plan #1
> -------
> After the document and OMF file are installed, scrollkeeper is informed
> (by way of a post-install script) where the document and the OMF file
> are at with something like:
> 
> scrollkeeper-install <docfile> <omffile>
> 
> Pro's: If people change where things get installed during installation of
> the package (and after the package is built), things do not break.
> 
> Con's: This requires one post-install script per document in the
> package.  It also requires that the packager keep track of the appropriate
> path variables.  (ie. it is a substantial burden on packagers)

By "per document", do you mean "per document", or do you mean "per file 
that might make up a document, such as if a FAQ is broken up in to 15
different files"?

If it's the former, I really don't see this being a huge problem.  It's
exactly what package maintainers have to do at the moment when they 
install a library, and need to run ldconfig afterwards.

In addition, I would expect most documentation for an application is
going to install in a subdirectory that's specific to that application.
So the package maintainer should be able to get away with something like

    scrollkeeper-update /usr/local/share/doc/app-name

and let scrollkeeper-update work out what to pull in.

As long as it's not more complicated than this process to manage info files,
we should be OK;

    http://www.freebsd.org/porters-handbook/porting-info.html

N
-- 
Internet connection, $19.95 a month.  Computer, $799.95.  Modem, $149.95.
Telephone line, $24.95 a month.  Software, free.  USENET transmission,
hundreds if not thousands of dollars.  Thinking before posting, priceless.
Somethings in life you can't buy.  For everything else, there's MasterCard.
  -- Graham Reed, in the Scary Devil Monastery