Re: Version 3.23 of Lout now re-installed

[Jeffrey Howard Kingston]

This is something of an oversight of mine.  I should include an
initializing run of Lout now in the lout.teq distribution, whose
sole real effect would be to create file texfonts.li.  After
creation this file remains constant for ever, since it is just
an index into file texfonts.ld which also remains constant.

Without the initializing run Lout will notice the absence of
the file and create it the first time it is needed.  This might
be a problem if write permission is not available in the
enclosing directory at that time.

File texfonts.lix is a temporary file, existing only while Lout
is running and creating texfonts.li.

Just emphasizing the main point: after the initialization there
is never any writing into system directories, here or anywhere
else in Lout.

Jeff


On Tue, 27 Jun 2000, Mike Dowling wrote:

> The first time lout-3.22 and lout-3.23 are called using teq-2.4, lout
> complains that /usr/local/share/lout/data/texfonts.lix and
> /usr/local/share/lout/data/texfonts.li don't exist.  Once created and
> made world readable and world writable, my experience was that, after a
> single run of lout, I could then remove the world writability.  Here, I
> set
> 
> LIBDIR  = /usr/local/share/lout
> 
> in the makefile.
> 
> Is this behaviour deliberate?
> 
> My suspicion is that were I to make more complex use of lout-teq, then I
> would once again have to make these files world writable, and I feel
> very uneasy about making system files world writable.
> 
> Cheers,
> Mike
> 
> 
>