Marek Rouchal writes:
> 3. Everything else must be searched in the current directory and
> directories provided in $TEXINPUTS, as these are probably home-brew.
In my case, I don't need *any* style or class files to be picked up
along TEXINPUTS, just document components. In fact, all document
components. ;-)
Here's the directory tree I'm using it now (some directories
omitted, since they're irrelevant to this discussion):
./Makefile control logic
./paper-a4/ build area for LaTeX, A4 paper
./paper-letter/ build area for LaTeX, US Letter paper
./html/ build area for LaTeX2HTML
api/, ext/, ... specific documents
./texinputs/ .cls, .sty, and boilerplate .tex files
./api/, ./ext/, ... .tex files for specific documents
I build with one of the paper-*/ directories as the current directory
for LaTeX, which produces the .aux file in that dir. The TEXINPUTS
environment variable looks something like
.:../paper-letter:../texinputs: at this point. I switch to html/ to
run latex2html, with TEXINPUTS set to the "right thing" (the same as
needed for LaTeX). I only need to have the .aux file and the .tex
files that are named using \input or \include searched along
TEXINPUTS. I can get the shared texinputs/ directory added to
$TEXINPUTS from my init file, but I don't see how to get the document
specific directory added. I can add some magic to the build process
to get the paper-*/ directory added from the init file, but that's
just not enough at the time the init file is loaded.
An after_initialization_hook() function would be useful, to be
called after all the command line parameters have been handled and the
jobname is known, but before calling texexpand.
Hmmm... that might be the best solution, since it can easily allow
just about any sort of tailoring that's needed, and would certainly
allow most of my problems to be easily handled rather than me raising
a big stink like this on the list. ;-)
-Fred
--
Fred L. Drake, Jr.
[EMAIL PROTECTED]
Corporation for National Research Initiatives
1895 Preston White Drive Reston, VA 20191
