Date:	Tue, 10 Nov 1998 15:14:53 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Boon van der RJ <rjvdboon AT cs DOT vu DOT nl>
cc:	djgpp AT delorie DOT com
Subject:	Re: ANNOUNCE: TeX/Web2c v7.2b ported and uploaded
In-Reply-To:	<72946t$l6r$1@star.cs.vu.nl>
Message-ID:	<Pine.SUN.3.91.981110150207.28101A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On 10 Nov 1998, Boon van der RJ wrote:

> >       tmflib74.zip -- the minimal TeX and Metafont library
> 
> But this file isn't on Simtel, while tmflib75.zip is. But tmflib75.zip
> contains version 7.4, as tmflib75.ver says.

Yes, the version mess caused the typo in the announcement.  The file name 
is correct, the version *is* 7.5, but the library claims to be version 
7.4 for some reason which beats me...

> By the way, is it intentional that some important directories
> (share/texmf and share/texmf/fonts) are unpacked with the read-only
> attribute set?

It's intentional: it causes the generated fonts to go to a different tree 
(%DJDIR%/var/texfonts, see the DJGPP-specific README file which explains 
that).  I feel that this is more convenient, since otherwise after 
running the programs for a while, you won't easily know which files 
inside the TEXMF tree were brought from outside, like CTAN and the 
Texmflib distribution, and which ones were generated on your machine.  
Being able to say which one is which makes maintenance easier, I think.  
For example, you could easily unpack a new Texmflib distribution without 
bothering about generated files.

I understand that you needed to remove the bit because you added 
additional font files from CTAN to the TEXMF tree, and needed to run 
mktexlsr after adding them.  If you want the generated fonts to go to 
%DJDIR%/var/texfonts, set the read-only bit again after running 
mktexlsr.  Alternatively, you could unpack the additional fonts to yet 
another tree, and add it to TEXMF variable (or define TEXMFLOCAL variable 
which is by default not defined).  Yet another alternative is to do what 
you did and leave TEXMF and TEXMF/fonts writable, so that generated fonts 
will be installed inside it.  It's entirely up to you.

In general, this release behaves much more predictably with multiple 
TEXMF trees, whereas the previous version required all kinds of 
non-trivial hacks unless you had a single large tree.  So I thought it 
would be a good idea to make some use of this even in the default setup.

- Raw text -