On Thu, 14 Oct 2004, Norman Gray wrote:
> Yes, if there's only a few, and (more importantly) they're not implicit
> in a macro (as the almost universal dependency on star2html is implicit
> in STAR_LATEX_DOCUMENTATION).
>
> I confess I'm a bit uncertain about where hlink comes in to the grand
> scheme of things. I vaguely thought that it was always (supposed to
> be) run after installing .htx docs, and that was why it was (rather,
> ought to be) a dependency on star2html. But as I say, running hlink
> after every .htx installation doesn't seem entirely sensible, so I'm
> happy if it has nothing to do with star2html at all!
>
> Anyone in proud possession of a Clue here (ie, not me) is quite welcome
> to edit STAR_LATEX_DOCUMENTATION if they believe it's doing the wrong
> or inadequate thing.
Norman,
yes, you should run hlink after every installation of a .htx document,
that creates the links to the local documents that exist, and, just as
importantly makes the other links point back to the main documentation set
at RAL.
The problem with this scheme is that it gets very slow quite quickly, so
the tendency has been to switch off hlink'ing during general installation
and then only run hlink once, when you know the documentation set is
complete.
Clearly when you're working on a single component hlink-ing can be useful
when you're modifying the documenation, and a pain at other times. The
moral seems to be that you need both options.
Peter.
|