Notes on TeX Live setup - Revision history

WikiSysop at 21:42, 16 July 2018

2018-07-16T21:42:24Z

Thanh: /* Keeping packages up-to-date */

2009-03-19T11:04:30Z

Keeping packages up-to-date

← Older revision		Revision as of 16:34, 19 March 2009
Line 105:		Line 105:
	There are 2 possible ways to keep packages up-to-date:		There are 2 possible ways to keep packages up-to-date:
	* using tlmgr: this is for real brave men; see [http://www.tug.org/texlive/doc/tlmgr.html tlmgr manual] and http://www.tug.org/texlive/tlmgr.html for further info.		* using tlmgr: this is for real brave men; see [http://www.tug.org/texlive/doc/tlmgr.html tlmgr manual] and http://www.tug.org/texlive/tlmgr.html for further info.
	* manual update: this is the simple, stupid way ~~for cowards like me~~. Let's update ie hyperref manually:		* manual update: this is the simple, stupid way that I prefer. Let's update ie hyperref manually:
	<geshi lang="bash">		<geshi lang="bash">
	mkdir -p /opt/texlive/tds-packages		mkdir -p /opt/texlive/tds-packages

Thanh: /* Keeping packages up-to-date */

2009-03-19T10:31:04Z

Keeping packages up-to-date

@@ Line 103: / Line 103: @@
 == Keeping packages up-to-date ==
-* Tell TL that we want to update packages from TL site:
+There are 2 possible ways to keep packages up-to-date:
 <geshi lang="bash">
-tlmgr option location http://mirror.ctan.org/systems/texlive/tlnet/2008
+mkdir -p /opt/texlive/tds-packages
 </geshi>
-* check which packages can be updated:
+* it's a good idea to keep the tds packages around, so that we know which packages have been installed this way.
 == Use non-TL binaries with TL data ==

Thanh: /* Introduction */

2009-03-19T10:05:05Z

Introduction

← Older revision		Revision as of 15:35, 19 March 2009
Line 2:		Line 2:
	This page describes steps to install [http://tug.org/texlive TeX Live] (TL from now) and needed tweaks so that other kpathsea programs that are not part of TL can also use TL data. This is useful if we recompile some program from sources and want it to be able to find TL data. For example, one might want to recompile pdftex with some patch, and use it instead of the binary coming with TL.		This page describes steps to install [http://tug.org/texlive TeX Live] (TL from now) and needed tweaks so that other kpathsea programs that are not part of TL can also use TL data. This is useful if we recompile some program from sources and want it to be able to find TL data. For example, one might want to recompile pdftex with some patch, and use it instead of the binary coming with TL.

	This guide was written for TL2008 on Ubuntu linux 8.01 and should work with no or little change for other Linux/UNIX systems.		This guide was written for TL2008 on Ubuntu linux 8.04 and should work with no or little change for other Linux/UNIX systems.

	When in doubt, please refer to the [http://www.tug.org/texlive/doc/texlive-en/texlive-en.html official TeX Live documentation]. This guide serves as a quick guide for some very specific purposes:		When in doubt, please refer to the [http://www.tug.org/texlive/doc/texlive-en/texlive-en.html official TeX Live documentation]. This guide serves as a quick guide for some very specific purposes:

Thanh: /* Keeping packages up-to-date */

2009-02-25T19:49:10Z

Keeping packages up-to-date

← Older revision		Revision as of 01:19, 26 February 2009
Line 121:		Line 121:
	* '''Recommendations for update''':		* '''Recommendations for update''':
	** don't update until you know why you have to (don't touch things that aren't broken)		** don't update until you know why you have to (don't touch things that aren't broken)
	** backup before update, so things can be reverted if needed. See [http://www.tug.org/texlive/doc/tlmgr.html tlmgr manual] for further info on backup/restore.		** backup before update, so things can be reverted if needed. See [http://www.tug.org/texlive/doc/tlmgr.html tlmgr manual] and http://www.tug.org/texlive/tlmgr.html for further info on backup/restore.
	** do '''not''' update all packages in one go		** do '''not''' update all packages in one go

Thanh: /* Run pdftex compiled from sources */

2009-02-04T09:47:12Z

Run pdftex compiled from sources

← Older revision		Revision as of 15:17, 4 February 2009
Line 205:		Line 205:
	pdflatex2 -ini -translate-file=cp227.tcx '*pdflatex.ini'		pdflatex2 -ini -translate-file=cp227.tcx '*pdflatex.ini'
	mv pdflatex.fmt /opt/texlive/2008/texmf-var/web2c/pdftex/pdflatex2.fmt		mv pdflatex.fmt /opt/texlive/2008/texmf-var/web2c/pdftex/pdflatex2.fmt

			texhash
	</geshi>		</geshi>
	* test the new binary:		* test the new binary:

Thanh: /* Run pdftex compiled from sources */

2009-02-04T09:42:03Z

Run pdftex compiled from sources

← Older revision		Revision as of 15:12, 4 February 2009
Line 190:		Line 190:
	ln -s $HOME/src/pdftex-1.40.9/build/texk/web2c/pdftex $HOME/bin/pdftex2		ln -s $HOME/src/pdftex-1.40.9/build/texk/web2c/pdftex $HOME/bin/pdftex2
	ln -s $HOME/src/pdftex-1.40.9/build/texk/web2c/pdftex $HOME/bin/pdflatex2		ln -s $HOME/src/pdftex-1.40.9/build/texk/web2c/pdftex $HOME/bin/pdflatex2
			</geshi>
			* find out the location of format files:
			<geshi lang="bash">
			ls -d $(dirname $(kpsewhich -engine=pdftex pdflatex.fmt) )
			/opt/texlive/2008/texmf-var/web2c/pdftex
	</geshi>		</geshi>
	* create formats:		* create formats:
	<geshi lang="bash">		<geshi lang="bash">
	cd ~~$(kpsewhich -expand-var '$TEXMFVAR')~~/~~web2c/pdftex~~		cd /tmp

	pdftex2 -ini -translate-file=cp227.tcx '*pdfetex.ini'		pdftex2 -ini -translate-file=cp227.tcx '*pdfetex.ini'
	mv pdfetex.fmt pdftex2.fmt		mv pdfetex.fmt /opt/texlive/2008/texmf-var/web2c/pdftex/pdftex2.fmt

	pdflatex2 -ini -translate-file=cp227.tcx '*pdflatex.ini'		pdflatex2 -ini -translate-file=cp227.tcx '*pdflatex.ini'
	mv pdflatex.fmt pdflatex2.fmt		mv pdflatex.fmt /opt/texlive/2008/texmf-var/web2c/pdftex/pdflatex2.fmt
	</geshi>		</geshi>
	* test the new binary:		* test the new binary:

Thanh: /* Some notes on some other relevant variables */

2008-10-21T08:23:10Z

Some notes on some other relevant variables

← Older revision		Revision as of 13:53, 21 October 2008
Line 172:		Line 172:
	TEXMF specifies which texmf trees are searched, and in which order. The order of the texmf trees given in '''TEXMF''' is important: earlier trees take precedence over the later ones in '''TEXMF'''.		TEXMF specifies which texmf trees are searched, and in which order. The order of the texmf trees given in '''TEXMF''' is important: earlier trees take precedence over the later ones in '''TEXMF'''.

	=== Some notes on ~~some~~ other relevant variables ===		=== Some notes on other relevant variables ===
	* '''TEXMFDBS''': contains list of texmf trees with '''ls-R''' filename databases. It's not clear how the presence of ls-R in a texmf tree and the presence of that tree in TEXMF and TEXMFDBS are related. To avoid potential problems, it's better to stick with either one of the below scenarios:		* '''TEXMFDBS''': contains list of texmf trees with '''ls-R''' filename databases. It's not clear how the presence of ls-R in a texmf tree and the presence of that tree in TEXMF and TEXMFDBS are related. To avoid potential problems, it's better to stick with either one of the below scenarios:
	** no ls-R, no presence of texmf tree in TEXMFDBS, presence in TEXMF without '''!!'''		** no ls-R, no presence of texmf tree in TEXMFDBS, presence in TEXMF without '''!!'''

Thanh: /* Use ls-R or not */

2008-10-20T21:16:36Z

Use ls-R or not

← Older revision		Revision as of 02:46, 21 October 2008
Line 158:		Line 158:

	=== Use ls-R or not ===		=== Use ls-R or not ===
	Each texmf tree can have a file called '''ls-R''' at the top level, which can help to speed up searching if the texmf tree is large. But using ls-R is not always the best option, since it requires some effort to get it right:		Each texmf tree can have a file called '''ls-R''' at the top level, which can help to speed up searching if the texmf tree is large. But using ls-R is not always the best option, since it requires some extra effort to get it right. If a texmf tree is small and changes often, it's better not to use ls-R. If a texmf tree is large, then it's worthwhile to go for the trouble.
	*

	~~Here is a quick summary of pros and cons which might help~~ to ~~decide whether~~ to ~~keep~~ ls-R ~~for a~~ texmf tree.		To use ls-R with the texmf tree in the previous example, we must:
			* edit texmf.cnf:
			** change '''$TEXMFTETEX''' to '''!!$TEXMFTETEX''' (only on one line -- the one starting with '''TEXMF = ...'''
			** add '''!!$TEXMFTETEX''' to TEXMFDBS
			* run '''texhash /opt/texlive/texmf-tetex''' to make ls-R in sync with the contents of texmf tree.

	~~==== With ls-R ====~~		Failing to do any of the above steps will cause that some files might not be found as expected, and it's not always easy to trace down the reason.
	* '''Pros'''
	** searching is fast
	* '''Cons'''
	** ls-R must be always in sync with the ~~texmf tree contents, otherwise~~ some files might not be found ~~(can be hard~~ to trace down)
	** some variables in texmf.~~cnf must be edited and kept in sync~~

	~~Some notes on~~ the ~~relevant variables above:~~		=== Change the order of file searching ===
	* '''TEXMF~~''':~~ specifies which texmf trees are searched, and in which order. The order of the texmf trees given in '''TEXMF''' is important: earlier trees take precedence over the later ones in '''TEXMF'''. ~~Edit '''texmf.cnf''' manually to change the order if needed.~~		If we need to change the precedence of a texmf tree, we can edit texmf.cnf and change the variable TEXMF.
	* '''TEXMFDBS''': contains list of texmf trees with '''ls-R''' filename databases. ~~Running~~ '~~''texhash''' without arguments will re~~-~~generate ''~~'ls-R~~''' for~~ texmf ~~trees listed~~ in '''~~TEXMFDBS~~'''~~. It's OK to have~~ ls-R in a tree ~~not listed~~ in TEXMFDBS~~; it will be used, but will not be updated by running~~ '''~~texhash~~'''.		TEXMF specifies which texmf trees are searched, and in which order. The order of the texmf trees given in '''TEXMF''' is important: earlier trees take precedence over the later ones in '''TEXMF'''.
	* '''SYSTEXMF''' (not listed above): contains a list of ''system'' texmf trees; its meaning is roughly this: if the source of a font is found in a system texmf tree and that tree is not writable for the current user, then the scripts '''mktexpk''', '''mktextfm''', and '''mktexmf''' will install their output into '''VARTEXFONTS''', otherwise the generated fonts (tfm/pk/mf) will be left in the current directory. If we are not using MF fonts, we can safely forget this variable. If we are using MF fonts and want the fonts generated on-the-fly to be placed to proper location, we must add the relevant texmf tree to SYSTEXMF. Usually not needed, since most TeX fonts are available in outline formats and when not, they can be easily converted from MF to Type1 format using '''textrace'''.
			=== Some notes on some other relevant variables ===
			* '''TEXMFDBS''': contains list of texmf trees with '''ls-R''' filename databases. It's not clear how the presence of ls-R in a texmf tree and the presence of that tree in TEXMF and TEXMFDBS are related. To avoid potential problems, it's better to stick with either one of the below scenarios:
			** no ls-R, no presence of texmf tree in TEXMFDBS, presence in TEXMF without '''!!'''
			** ls-R in sync with contents of texmf tree, presence in TEXMF and TEXMFDBS with '''!!'''
			* '''SYSTEXMF''' (not listed above): contains a list of ''system'' texmf trees; its meaning is roughly this: if the source of a font is found in a system texmf tree and that tree is not writable for the current user, then the scripts '''mktexpk''', '''mktextfm''', and '''mktexmf''' will install their output into '''VARTEXFONTS''', otherwise the generated fonts (tfm/pk/mf) will be left in the current directory. If we are not using MF fonts, we can safely forget this variable. If we are using MF fonts and want the fonts generated on-the-fly to be placed to proper location, we must add the relevant texmf tree to SYSTEXMF. Usually not needed, since most TeX fonts are available in outline formats and when not, they can be easily converted from MF to Type1 format using '''textrace'''. It is best if we can avoid touching this variable.

	== Run pdftex compiled from sources ==		== Run pdftex compiled from sources ==

Thanh: /* Add another texmf tree */

2008-10-20T20:46:59Z

Add another texmf tree

@@ Line 150: / Line 150: @@
 * locate the path to the texmf tree, and make a symlink in '''/opt/texlive'''
 * adjust the above commands accordingly.
 Or, it is possible to use [http://download.river-valley.com/add-texmf-tree.sh this script] to automate the above steps. Usage:
@@ Line 156: / Line 155: @@
 sh add-texmf-tree.sh TEXMFTETEX /opt/texlive/texmf-tetex /opt/texlive/2008/texmf.cnf
 </geshi>
 Some notes on the relevant variables above: