Randy McMurchy wrote: > Hi all, > > I'd like to propose some changes to the TeX-3.0 instructions. Some > to fix brokenness, others for learning advantages to the builder and > one because I just feel it is the "right thing". > > 1) The following two commands don't work as they should: > > TEXMFVAR=/usr/share/texmf-var texconfig dvips paper letter && > TEXMFVAR=/usr/share/texmf-var texconfig font rw > > Problem is two things. Passing the envar doesn't help, and it is > using the wrong command anyway. Removing passing the envar and changing > the commands to 'texconfig-sys' instead of 'texconfig' achieves the > desired result of updating the system-wide TeX configuration and > not creating a private TeX configuration directory.
Excellent observation. I like this a lot better. > 2) I would like to change the following command: > > FONTDIR=/usr/share/texmf/ && > > to > > FONTDIR=$(kpsewhich --expand-var '$TEXMFMAIN') && > > Two benefits: one, it is using TeX commands to find out where the > installation is (learning advantage) and two, if someone changed > the installation prefix, the command still works. Sounds good. > 3) The following command is broken: > > cat >> $FONTDIR/texmf/web2c/updmap.cfg << "EOF" && > > because the $FONTDIR/texmf directory doesn't exist. The texmf/ in > the path should be removed. The command should be: > > cat >> $FONTDIR/web2c/updmap.cfg << "EOF" && You are right. I missed this when I wrote up the instructions for cm-super fonts. > 4) This command is actually a misuse: > > TEXMFVAR=/usr/share/texmf-var updmap && > > It should be changed to this: > > mktexlsr && > updmap-sys && > > The mktexlsr command must be run to update the TeX ls-R database. Then > the updmap-sys command is run (instead of the updmap command) so that > the system-wide update program is used. I did it this way and it worked > perfectly. All font maps were found and it updated the system-wide > configuration. OK. I got the original instructions from Alexander. Yours are better. > 5) Lastly, I think the CM-Super font installation is a bit confusing > because the way the commands are, they are based on the fact of issuing > them from *outside* the package source directory. I don't believe this is true. We don't normally provide the tar command to extract files. If we assume we are in the package source directory when we do the untar, then the commands are (with the extra texmf removed) correct. Actually, the commands given are valid independent of the starting directory. I believe they should > be changed to reflect being *inside* the source directory (as we do on > every other installation I can think of). There should be an explanatory > sentence as well guiding the builder to change out of the tetex-src-3.0 > directory and into the cm-super directory. Perhaps we should just specify: tar -xf ../tetex-cm-super.tar.bz2 as the first command of this subsection. Since I did the cm-super font addition, I can update this section. but since you did all this reserach, you can do it if you want. Your call. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
