[l2h] Minor installation problem (2K.1beta)

Ross Moore ross@ics.mq.edu.au
Thu, 22 Mar 2001 20:16:09 +1100 (EST)

> >>>>> "RM" == Ross Moore <ross@ics.mq.edu.au> writes:
>     RM> No.  ICONPATH and ICONSERVER are completely independent bits
>     RM> of information.

> I find it difficult to believe that Ross is wrong, but this is at
> variance to what the file prefs.pm says:-

Oops; don't you believe it.
I'm getting careless with increasing age.  :-)

$ICONSTORAGE is correct for how I described ICONPATH .

> # If left empty, an appropriate file: URL is assumed. This will show
> # the icons o.k. on your local host, but won't work across the Web.
> $prefs{'ICONPATH'} = 'http://www.cs.man.ac.uk/software/latex2html/icons';
> # This is the directory where the icons have to be copied so that they
> # can be accessed with the path given above. Keep this empty if you do
> # not want the icons to be installed in your Web server area.
> # However, the icons are installed in LIBDIR/icons, no matter what.
> $prefs{'ICONSTORAGE'} = '';
> and l2hconf.pin has the line

On a solaris installation, I have lines:

l2hconf.pin:123:#$ICONSERVER = '@ICONPATH@';
l2hconf.pin:124:$ICONSERVER = "http://www.maths.mq.edu.au/texdev/images";

so it could be that the interpolation of  @ICONPATH@  isn't working properly.

> Maybe my problem is related to the lines in prefs.pm which say:-
> # The file prefs.pm contains user-configurable stuff for DOS platforms.
> # UNIX users can override the settings with the configure utility (preferred).
> which suggests that prefs.pm isn't used on Unix platforms. However, in
> the UNIX section of the INSTALL file it tells you to edit prefs.pm,

Marek used to handle all the installation stuff.
We haven't heard from him for awhile; since the baby arrived.

There'll soon be a need for more alterations to the installation,
to take account of the revised  pnmcrop  at sourceforge.net .
I submitted a patch last week-end to recover the desired cropping ability.
It should appear as v9.12 any time now.

> It would appear that there is some confusion here, and I don't think
> it's all mine, although I'm perfectly prepared to believe that
> some/most of it is!

It would be good to have some fresh eyes looking at the whole installation,
mainly to adapt to new versions of some of the software,
and to ensure that there are consistent instructions across platforms.

All the best,

and I apologise for my mistaken explanation.


> Regards
> Graham