According to Richard L Jackson Jr:
> Under latex2html 96.1 I was able to point $PBMPLUSDIR, in latex2html.config,
> to /usr/local/netpbm/bin, the location of the zillion netpbm binaries.
> latex2html 98.1pl1 does not seem to support this. Does this mean I must
> have latex2html users add /usr/local/netpbm/bin to their search path or
> move the files out of hiding into a general directory, /usr/local/bin,
> that is already in everyones search path? Are there any better options?
I would have thought that if you ensured that
/usr/local/netpbm/bin was in your path before running test-install
then the appropriate variable in latex2html.config would be
automatically updated ... did you try this?
Irrespective of whether you can/can't do this, why don't you make
the binaries easy for any user to find? By all means keep them in
/usr/local/netpbm/bin but consider adding links to them in
/usr/local/bin ... in tcsh one can do in /usr/local/bin
foreach a (/usr/local/netpbm/bin/*)
? ln -s $a $a:t
? end
(The `?'s are prompts while in foreach.) This has the pleasant
properties of:
1. Putting binaries in an obvious place where everyone can
find them.
2. Doing an `ls -l' of the /usr/local/bin directory tells
you *exactly* with which piece of software a given binary belongs.
(This also means it's easy to identify *all* the bits of a
piece of software that needs to be upgraded.)
It really is annoying not being able to use which or whereis to
locate some software purely because it's not already in one's path.
I have accounts at two different institutions ... at one I have to
set explicitly in my .cshrc to include in my path:
/opt/local/gnu/bin to get perl and /opt/netscape-3.04/bin to get netscape
etc. etc. ... my path at this instution continues over 23 lines!
At the other institution they follow the policy above ... my path
easily fits on one line! ... and what's more there is no work to do
trying to figure out what my path ought to be at any time ... if a
new piece of software is added, I know it will already be in my path!
I know which policy I prefer!
Regards,
Greg Gamble <[EMAIL PROTECTED]>
