* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2012-10-28 15:21 Sven Vermeulen (swift)
0 siblings, 0 replies; 7+ messages in thread
From: Sven Vermeulen (swift) @ 2012-10-28 15:21 UTC (permalink / raw
To: gentoo-commits
swift 12/10/28 15:21:17
Modified: texlive-migration-guide.xml
Log:
Removing link attribute from guides
Revision Changes Path
1.8 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.7&r2=1.8
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- texlive-migration-guide.xml 15 Apr 2009 05:59:09 -0000 1.7
+++ texlive-migration-guide.xml 28 Oct 2012 15:21:16 -0000 1.8
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.7 2009/04/15 05:59:09 aballier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.8 2012/10/28 15:21:16 swift Exp $ -->
-<guide link="/proj/en/tex/texlive-migration-guide.xml">
+<guide>
<title>TeX Live 2008 guide</title>
<author title="Author">
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2009-04-15 5:59 Alexis Ballier (aballier)
0 siblings, 0 replies; 7+ messages in thread
From: Alexis Ballier (aballier) @ 2009-04-15 5:59 UTC (permalink / raw
To: gentoo-commits
aballier 09/04/15 05:59:09
Modified: texlive-migration-guide.xml
Log:
add a note about the need to run texmf-update after touching files in /etc/texmf/*.d because this seems to be a common mistake
Revision Changes Path
1.7 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.6&r2=1.7
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- texlive-migration-guide.xml 3 Apr 2009 23:04:33 -0000 1.6
+++ texlive-migration-guide.xml 15 Apr 2009 05:59:09 -0000 1.7
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.6 2009/04/03 23:04:33 fauli Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.7 2009/04/15 05:59:09 aballier Exp $ -->
<guide link="/proj/en/tex/texlive-migration-guide.xml">
<title>TeX Live 2008 guide</title>
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.4</version>
-<date>2009-04-04</date>
+<version>1.5</version>
+<date>2009-04-15</date>
<chapter id="uninstall">
<title>Clean uninstall</title>
@@ -487,7 +487,9 @@
in <path>/etc/texmf/texmf.d</path>. This will most likely be due to an
old <path>00texmf.cnf</path> being still there and thus setting wrong
definitions for the <path>texmf.cnf</path> file. Please refer to the
-<uri link="#uninstall">Clean uninstall chapter </uri>.
+<uri link="#uninstall">Clean uninstall chapter</uri> and remember that when you
+modify or remove a file in <path>/etc/texmf/*.d</path> you need to run
+<c>texmf-update</c> to have the changes taken into account.
</p>
</body>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2009-04-03 23:04 Christian Faulhammer (fauli)
0 siblings, 0 replies; 7+ messages in thread
From: Christian Faulhammer (fauli) @ 2009-04-03 23:04 UTC (permalink / raw
To: gentoo-commits
fauli 09/04/03 23:04:33
Modified: texlive-migration-guide.xml
Log:
Update to TeXLive 2008 (just changing numbers)
Revision Changes Path
1.6 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.5&r2=1.6
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- texlive-migration-guide.xml 14 Nov 2008 09:54:26 -0000 1.5
+++ texlive-migration-guide.xml 3 Apr 2009 23:04:33 -0000 1.6
@@ -1,16 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.5 2008/11/14 09:54:26 aballier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.6 2009/04/03 23:04:33 fauli Exp $ -->
<guide link="/proj/en/tex/texlive-migration-guide.xml">
-<title>TeX Live 2007 guide</title>
+<title>TeX Live 2008 guide</title>
<author title="Author">
<mail link="aballier@gentoo.org">Alexis Ballier</mail>
</author>
<abstract>
-This guide aims to show you how to install TeX Live 2007 on Gentoo,
+This guide aims to show you how to install TeX Live 2008 on Gentoo,
more specifically what you need to take care of if you already have a
TeX distribution installed (like tetex or TeX Live 2005).
</abstract>
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.3</version>
-<date>2008-11-14</date>
+<version>1.4</version>
+<date>2009-04-04</date>
<chapter id="uninstall">
<title>Clean uninstall</title>
@@ -119,7 +119,7 @@
<p>
<c>tetex</c> was also using <c>fmtutil</c> outside of the scope of the package
-manager to generate the format files. With <c>TeX Live 2007</c> we now
+manager to generate the format files. With <c>TeX Live 2008</c> we now
build most of the format files while compiling the packages; which format
files will be installed in <path>/var/lib/texmf</path>. That means you have to
make sure that there are no stray format files:
@@ -134,16 +134,16 @@
</chapter>
<chapter>
-<title>Installing TeX Live 2007</title>
+<title>Installing TeX Live 2008</title>
<section>
<body>
<p>
If you have passed through all the above steps, installing <c>TeX Live
-2007</c> now should be very easy.
+2008</c> now should be very easy.
</p>
-<pre caption="Install TeX Live 2007">
+<pre caption="Install TeX Live 2008">
# <i>emerge texlive</i>
</pre>
@@ -214,7 +214,7 @@
<p>
This is the result of the splitting in their respective sections of a
(lightly) modified <path>texmf.cnf</path> file from <c>TeX Live
-2007</c> DVD.
+2008</c> DVD.
</p>
<p>
@@ -460,7 +460,7 @@
<pre caption="Format directory does not exist">
fmtutil: format directory
-`/var/tmp/portage/dev-texlive/texlive-latex-2007/work/texmf-var/web2c' does not
+`/var/tmp/portage/dev-texlive/texlive-latex-2008/work/texmf-var/web2c' does not
exist.
</pre>
@@ -506,7 +506,7 @@
Local configuration file hyphen.cfg used
===========================================
-(/var/tmp/portage/dev-texlive/texlive-latex-2007/work/texmf-dist/tex/generic/ba
+(/var/tmp/portage/dev-texlive/texlive-latex-2008/work/texmf-dist/tex/generic/ba
bel/hyphen.cfg (/usr/share/texmf/tex/generic/hyphen/hyphen.tex)
(/usr/share/texmf/tex/generic/hyphen/ushyphmax.tex)
(/usr/share/texmf/tex/generic/hyphen/dumyhyph.tex)
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2008-11-14 9:54 Alexis Ballier (aballier)
0 siblings, 0 replies; 7+ messages in thread
From: Alexis Ballier (aballier) @ 2008-11-14 9:54 UTC (permalink / raw
To: gentoo-commits
aballier 08/11/14 09:54:26
Modified: texlive-migration-guide.xml
Log:
add a note about the new location of language.*.dat files for tl2008, refs bug #246378
Revision Changes Path
1.5 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.4&r2=1.5
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- texlive-migration-guide.xml 30 Sep 2008 21:00:41 -0000 1.4
+++ texlive-migration-guide.xml 14 Nov 2008 09:54:26 -0000 1.5
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.4 2008/09/30 21:00:41 aballier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.5 2008/11/14 09:54:26 aballier Exp $ -->
<guide link="/proj/en/tex/texlive-migration-guide.xml">
<title>TeX Live 2007 guide</title>
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.2</version>
-<date>2008-09-30</date>
+<version>1.3</version>
+<date>2008-11-14</date>
<chapter id="uninstall">
<title>Clean uninstall</title>
@@ -541,7 +541,9 @@
<p>
This file is automatically generated by <c>texmf-update</c> and is the
result of concatenating <path>language.*.dat</path> files present in
-the directory with <path>language.us</path>. This directory should be
+the directory with <path>language.us</path> (for TeX Live 2008, the
+<path>language.*.dat</path> files are taken from
+<path>/etc/texmf/language.dat.d/</path>). This directory should be
<path>/usr/share/texmf/tex/generic/config/</path>. So you should check
that there are no other <path>language.*.dat</path> files in that
directory other than the ones installed by the various
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2008-09-30 21:00 Alexis Ballier (aballier)
0 siblings, 0 replies; 7+ messages in thread
From: Alexis Ballier (aballier) @ 2008-09-30 21:00 UTC (permalink / raw
To: gentoo-commits
aballier 08/09/30 21:00:42
Modified: texlive-migration-guide.xml
Log:
suggest ~ as backup location for tetex config files instead of /tmp
Revision Changes Path
1.4 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.3&r2=1.4
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- texlive-migration-guide.xml 30 Mar 2008 10:33:30 -0000 1.3
+++ texlive-migration-guide.xml 30 Sep 2008 21:00:41 -0000 1.4
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.3 2008/03/30 10:33:30 aballier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.4 2008/09/30 21:00:41 aballier Exp $ -->
<guide link="/proj/en/tex/texlive-migration-guide.xml">
<title>TeX Live 2007 guide</title>
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.1</version>
-<date>2008-03-30</date>
+<version>1.2</version>
+<date>2008-09-30</date>
<chapter id="uninstall">
<title>Clean uninstall</title>
@@ -48,7 +48,7 @@
</p>
<pre caption="Save your old configuration files">
-$ <i>cp -rf /etc/texmf /tmp/tetex-texmf</i>
+$ <i>cp -rf /etc/texmf ~/tetex-texmf</i>
</pre>
</body>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2008-03-30 10:33 Alexis Ballier (aballier)
0 siblings, 0 replies; 7+ messages in thread
From: Alexis Ballier (aballier) @ 2008-03-30 10:33 UTC (permalink / raw
To: gentoo-commits
aballier 08/03/30 10:33:30
Modified: texlive-migration-guide.xml
Log:
Update by John Christian Stoddart: grammar and simpler way of removing dead symlinks.
Revision Changes Path
1.3 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.2&r2=1.3
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- texlive-migration-guide.xml 9 Mar 2008 12:41:24 -0000 1.2
+++ texlive-migration-guide.xml 30 Mar 2008 10:33:30 -0000 1.3
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.2 2008/03/09 12:41:24 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.3 2008/03/30 10:33:30 aballier Exp $ -->
<guide link="/proj/en/tex/texlive-migration-guide.xml">
<title>TeX Live 2007 guide</title>
@@ -10,17 +10,17 @@
</author>
<abstract>
-This guide aims to show you how to install TeX Live 2007 on Gentoo, more
-specifically what you need to take care of if you already had a TeX distribution
-installed (like tetex or TeX Live 2005).
+This guide aims to show you how to install TeX Live 2007 on Gentoo,
+more specifically what you need to take care of if you already have a
+TeX distribution installed (like tetex or TeX Live 2005).
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.0</version>
-<date>2007-12-20</date>
+<version>1.1</version>
+<date>2008-03-30</date>
<chapter id="uninstall">
<title>Clean uninstall</title>
@@ -31,9 +31,9 @@
<p>
In this section we will assume that you have <c>>=app-text/tetex-3</c>
-installed. This applies as well if you had installed
-<c>app-text/texlive-2005</c>. In a perfect world it would be as simple as
-unmerging it, but unfortunately it is not.
+installed. This also applies if you had <c>app-text/texlive-2005</c>
+installed. In a perfect world it would be as simple as unmerging it,
+but unfortunately it is not.
</p>
</body>
@@ -43,8 +43,8 @@
<body>
<p>
-If you had modified your configuration of <c>tetex</c> by editing files in
-<path>/etc/texmf</path>, you should first save them:
+If you have modified your configuration of <c>tetex</c> editing the
+files in <path>/etc/texmf</path>, you should save them first:
</p>
<pre caption="Save your old configuration files">
@@ -58,7 +58,7 @@
<body>
<p>
-Then you can unmerge safely <c>tetex</c>:
+Now you can safely unmerge <c>tetex</c>:
</p>
<pre caption="Remove tetex">
@@ -66,9 +66,9 @@
</pre>
<p>
-Some weird errors have been reported when there were stray configuration files
-left in <path>/etc/texmf</path>. For safety and a clean install of <c>TeX
-Live</c> it is recommended to remove the
+Some weird errors have been reported when stray configuration files
+were left behind in <path>/etc/texmf</path>. For safety and for a
+clean install of <c>TeX Live</c> it is recommended to remove the
<path>/etc/texmf/texmf.d/00texmf.cnf</path> file:
</p>
@@ -81,8 +81,9 @@
</note>
<p>
-Due to <c>tetex</c> using <c>texlinks</c> outside of the scope of the package
-manager, simply unmerging it will have left some stray symlinks:
+Due to <c>tetex</c> using <c>texlinks</c> outside of the scope of the
+package manager, simply unmerging it will have left behind some stray
+symlinks:
</p>
<pre caption="tetex stray symlink">
@@ -92,32 +93,34 @@
<p>
Of course, pdfetex has gone with <c>tetex</c>'s removal, so the pdftex symlink
-is a dead one. It can be safely removed. The <c>find</c> command can help
-finding dead symlinks (with a GNU extension though):
+is dead and can be safely removed. The <c>find</c> command (with a GNU
+extension though) can help us find and remove dead symlinks interactively:
</p>
-<pre caption="Find dead symlinks">
-$ <i>find /usr/bin -type l ! -xtype f ! -xtype d</i>
+<pre caption="Eliminate dead symlinks interactively">
+# <i>find /usr/bin -type l ! -xtype f ! -xtype d -ok rm -f {} \;</i>
-/usr/bin/lamed
-/usr/bin/latex
-/usr/bin/amstex
-/usr/bin/elatex
-/usr/bin/eplain
-/usr/bin/lambda
-/usr/bin/pdftex
-/usr/bin/pdflatex
-/usr/bin/pdfamstex
+< rm ... /usr/bin/pdflatex > ? y
+< rm ... /usr/bin/amstex > ? y
+< rm ... /usr/bin/pdftex > ? y
+< rm ... /usr/bin/eplain > ? y
+< rm ... /usr/bin/jadetex > ? y
+< rm ... /usr/bin/lambda > ? y
+< rm ... /usr/bin/pdfamstex > ? y
+< rm ... /usr/bin/elatex > ? y
+< rm ... /usr/bin/lamed > ? y
+< rm ... /usr/bin/pdfjadetex > ? y
+< rm ... /usr/bin/latex > ? y
</pre>
<p>
-These are the files left over by my <c>tetex</c> installation.
+These were the files left over by my <c>tetex</c> installation.
</p>
<p>
<c>tetex</c> was also using <c>fmtutil</c> outside of the scope of the package
-manager to generate the format files. With <c>TeX Live 2007</c> we are now
-building most of the format files while compiling the packages; which format
+manager to generate the format files. With <c>TeX Live 2007</c> we now
+build most of the format files while compiling the packages; which format
files will be installed in <path>/var/lib/texmf</path>. That means you have to
make sure that there are no stray format files:
</p>
@@ -136,8 +139,8 @@
<body>
<p>
-If you have passed through all the above steps, now installing <c>TeX Live
-2007</c> should be very easy.
+If you have passed through all the above steps, installing <c>TeX Live
+2007</c> now should be very easy.
</p>
<pre caption="Install TeX Live 2007">
@@ -145,19 +148,20 @@
</pre>
<p>
-In theory this should just go smoothly and install everything. You might want at
-some point to tune <c>app-text/texlive</c> use flags to install extra TeX
-packages, but you can do it later; <c>app-text/texlive</c> is just a meta-ebuild
-that pulls the real packages depending on its use flags.
+In theory this should just go smoothly and install everything. You
+might want to tune <c>app-text/texlive</c> USE flags to install extra
+TeX packages, but you can do it later; <c>app-text/texlive</c> is just
+a meta-ebuild that pulls the real packages depending on its USE flags.
</p>
<p>
-Nevertheless, it is possible that you get dependencies problems, errors while
-installing a package, etc. In that case, you are advised to file a bug on
-<uri>https://bugs.gentoo.org</uri>. If you do file a bug, please include at
-least the output of <c>texconfig conf</c> (run as the same user that failed to
-install because some environment variables might be important) in addition to
-the error; this output will most often be requested.
+Nevertheless, it is possible to get dependency problems, errors while
+installing a package, etc. In that case, you are advised to file a bug
+on <uri>https://bugs.gentoo.org</uri>. If you file a bug, please
+include at least the output of <c>texconfig conf</c> (run as the same
+user that failed to install, because some environment variables might
+be important) in addition to the error; this output will most often be
+requested.
</p>
</body>
@@ -171,12 +175,12 @@
<body>
<p>
-As it was the case for <c>tetex-3</c>, <c>TeX Live</c> on <c>Gentoo</c> has its
-three main configuration files splitted and handled by <c>texmf-update</c>.
+As was the case for <c>tetex-3</c>, <c>TeX Live</c> on <c>Gentoo</c> has its
+three main configuration files separated and handled by <c>texmf-update</c>.
These files are, namely, <path>texmf.cnf</path>, <path>fmtutil.cnf</path>,
<path>updmap.cfg</path>. They lie in <path>/etc/texmf/web2c</path>; you should
not modify them directly because the changes will be lost the next time
-<c>texmf-update</c> is ran.
+<c>texmf-update</c> is run.
</p>
</body>
@@ -186,13 +190,13 @@
<body>
<p>
-The <path>texmf.cnf</path> configuration file is the main configuration file for
-your TeX installation, it contains various variable definitions that will be
-used by a lot of programs.
+The <path>texmf.cnf</path> file is the main TeX installation
+configuration file. It contains variable definitions that will be used
+by a lot of programs.
</p>
<p>
-The <path>texmf.cnf</path> file is the result of the concatenation of the files
+The <path>texmf.cnf</path> file is the result of concatenating files
in <path>/etc/texmf/texmf.d</path>. In order to modify your TeX environment
configuration, you should modify the files there. At the time of writing,
<c>Gentoo TeX Live</c>'s ebuild install six files there:
@@ -208,40 +212,44 @@
</pre>
<p>
-This is the result of the splitting in their respective sections of a (lightly)
-modified <path>texmf.cnf</path> file from <c>TeX Live 2007</c> DVD.
+This is the result of the splitting in their respective sections of a
+(lightly) modified <path>texmf.cnf</path> file from <c>TeX Live
+2007</c> DVD.
</p>
<p>
-The files <path>00header.cnf</path>, <path>05searchpaths.cnf</path>,
-<path>10standardpaths.cnf</path> and <path>25misc.cnf</path> should not be
-modified and kept as is. If the defaults can be improved, please file a bug.
+The <path>00header.cnf</path>, <path>05searchpaths.cnf</path>,
+<path>10standardpaths.cnf</path> and <path>25misc.cnf</path> files
+should not be modified. If the defaults can be improved, please file a
+bug.
</p>
<warn>
-The <c>TeX Live</c> ebuilds are not aware of paths changes of those files, so if
-yuu change any path there, make sure you know what you are doing.
+The <c>TeX Live</c> ebuilds are not aware of path changes of those
+files, so if you change any path there, make sure you know what you
+are doing.
</warn>
<p>
-The files <path>15options.cnf</path> and <path>20sizes.cnf</path> can be
-modified with caution. The comments in these files should be explicit of what
-option means what. For example, in <path>20sizes.cnf</path> you can increase TeX
-memory, in case you are trying to compile a too big document and run into <c>TeX
-capacity exceeded, sorry</c> errors.
+The <path>15options.cnf</path> and <path>20sizes.cnf</path> files can
+be modified with caution. The comments in these files should explain
+what options mean. For example, in <path>20sizes.cnf</path> you can
+increase TeX memory, in case you are trying to compile a document that
+is too big and runs into <c>TeX capacity exceeded, sorry</c> errors.
</p>
<p>
-If you wish to append some additions to the <path>texmf.cnf</path> file, you can
-also create a new file in <path>/etc/texmf/texmf.d</path>, called for example
-<path>99myadditions.cnf</path>. Beware though to not give it a higher priority
-than the core configuration files, so it should begin with a two digits number
-greater than <c>25</c>.
+If you wish to append additions to the <path>texmf.cnf</path> file,
+you can also create a new file in <path>/etc/texmf/texmf.d</path>,
+called for example <path>99myadditions.cnf</path>. Beware not to give
+it a higher priority than the core configuration files, so it should
+begin with a two digit number greater than <c>25</c>.
</p>
<p>
-Packages that need to append something to the <path>texmf.cnf</path> file get
-the same treatment, they should install a <path>texmf.d</path> file instead:
+Packages that need to append something to the <path>texmf.cnf</path>
+file get the same treatment, they should install a
+<path>texmf.d</path> file instead:
</p>
<pre caption="Sample code for installing a texmf.d file">
@@ -256,43 +264,46 @@
<body>
<p>
-The <path>updmap.cfg</path> is the configuration file used by <c>updmap</c> (and
-<c>updmap-sys</c>), unless otherwise specified. It tells it which font maps to
-update for the various TeX output drivers.
+The <path>updmap.cfg</path> file is the configuration file used by
+<c>updmap</c> (and <c>updmap-sys</c>), unless otherwise specified. It
+tells it which font maps to update for the various TeX output drivers.
</p>
<p>
-The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is the result
-of the concatenation of the files in <path>/etc/texmf/updmap.d</path>. The
-initial <path>00updmap.cfg</path> file installed by <c>app-text/texlive-core</c>
-is the result of <c>updmap --syncwithtrees</c> ran on the <c>texmf</c> tree that
-it installs (in fact, it just mimics what <c>updmap --syncwithtrees</c> would
-do, but it is only a technical detail).
+The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is
+the result of concatenating the files in
+<path>/etc/texmf/updmap.d</path>. The initial
+<path>00updmap.cfg</path> file installed by
+<c>app-text/texlive-core</c> is the result of running <c>updmap
+--syncwithtrees</c> on the the installed <c>texmf</c> tree (in fact,
+it just mimics what <c>updmap --syncwithtrees</c> would do, but it is
+only a technical detail).
</p>
<p>
Various <c>TeX Live</c> ebuilds will add files to the
-<path>/etc/texmf/updmap.d</path> directory, when they install fonts. While you
-can edit those files to disable some font maps to be updated, it would probably
-be wiser to remove the relevant package.
+<path>/etc/texmf/updmap.d</path> directory when they install
+fonts. While you can edit those files to disable some font maps to be
+updated, it would probably be wiser to remove the relevant package.
</p>
<p>
-If a third party package wants to add some font maps, it should install a file
-in <path>/etc/texmf/updmap.d</path> and let <c>texmf-update</c> handle it.
+If a third party package wants to add font maps, it should
+install a file in <path>/etc/texmf/updmap.d</path> and let
+<c>texmf-update</c> handle it.
</p>
<warn>
-Sometimes you can see <c>updmap-sys --enable Map=mymap.map</c> in some ebuilds
-or some installation instructions of a third party font package, while this
-might work at a first try, the changes will be reverted the next time
-<c>texmf-update</c> is ran.
+Sometimes you can see <c>updmap-sys --enable Map=mymap.map</c> in some
+ebuilds or some installation instructions of a third party font
+package, while this might work at first, these changes will be
+reverted the next time <c>texmf-update</c> is run.
</warn>
<p>
-The good way of handling it would be to create a file to be installed in
-<path>/etc/texmf/updmap.d</path> and install it for TeX distributions that
-support the <c>texmf-update</c> way:
+A better way of handling this would be to create a file to be
+installed in <path>/etc/texmf/updmap.d</path> and install it for TeX
+distributions that support the <c>texmf-update</c> way:
</p>
<pre caption="How to enable a font map">
@@ -338,15 +349,15 @@
<body>
<p>
-The <path>fmtutil.cnf</path> file contains the information on how to build a
-format file and how to handle it.
+The <path>fmtutil.cnf</path> file contains information on how to
+build and handle a format file.
</p>
<p>
-The <path>fmtutil.cnf</path> file is the result of the concatenation of the
-files in <path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c> ebuilds
-install files there, those files come with the formats they add support for and
-the symlink to the relevant engine.
+The <path>fmtutil.cnf</path> file is the result of concatenating the
+files in <path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c>
+ebuilds install files there. Those files come with the formats they
+add support for and the symlink to the relevant engine.
</p>
<pre caption="Snippet of the fmtutil.cnf(5) man page that explains the syntax">
@@ -365,16 +376,16 @@
</pre>
<p>
-<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file install the
-relevant format files in <path>/var/lib/texmf/web2c</path> and create the
-symlink from the format to the engine.
+<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file,
+install the relevant format files in <path>/var/lib/texmf/web2c</path>
+and create the symlink from the format to the engine.
</p>
<p>
-It should be noted that when a support file for a language gets added,
-<c>texmf-update</c> takes care of adding it to the <path>language.dat</path>
-file and regenerates the format files so that they support the newly installed
-language.
+Note that when a support file for a language gets added,
+<c>texmf-update</c> takes care of adding it to the
+<path>language.dat</path> file and regenerates the format files to
+support the newly installed language.
</p>
</body>
@@ -384,9 +395,10 @@
<body>
<p>
-Now that you know how <c>TeX Live</c> configuration is managed, you should be
-able to port the changes you had made to your older TeX distribution
-configuration to the <c>TeX Live</c> configuration layout.
+Now that you know how <c>TeX Live</c> configuration is managed, you
+should be able to port the changes you had made to your older TeX
+distribution configuration to the <c>TeX Live</c> configuration
+layout.
</p>
</body>
@@ -400,8 +412,8 @@
<body>
<p>
-In this chapter we will try to give a short summary of the most common errors
-and explain what has gone wrong.
+In this chapter we will try to give a short summary of the most common
+errors and explain what has gone wrong.
</p>
</body>
@@ -411,8 +423,8 @@
<body>
<p>
-Sometimes when installing some packages that requires latex, you'll get this
-error:
+Sometimes when installing some packages that requires latex, you'll
+get this error:
</p>
<pre caption="Format was written by pdfetex">
@@ -421,14 +433,14 @@
<p>
This is due to old files remaining from an old installation of a <c>TeX</c>
-distribution based on <c>etex</c>. That most likely means you did not follow
+distribution based on <c>etex</c>. This most likely means you did not follow
entirely this guide, especially the <uri link="#uninstall">Clean uninstall
chapter</uri>.
</p>
<p>
-Nevertheless, it is still possible to fix it quickly without having to reinstall
-anything, just run as root:
+Nevertheless, it is still possible to fix it quickly without having to
+reinstall anything, just run as root:
</p>
<pre caption="Remove old formats">
@@ -453,8 +465,8 @@
</pre>
<p>
-This is most likely to be due to a wrong configuration. You should try to run
-the following command and get the same results:
+This is most likely due to a wrong configuration. Try to run the
+following command and get the same results:
</p>
<pre caption="TEXMFMAIN definition">
@@ -463,19 +475,19 @@
</pre>
<p>
-This is very important, since <c>fmtutil</c> looks for <c>mktexdir</c> at this
-location; if you have a different result then <c>fmtutil</c> will not find
-<c>mktexdir</c> and thus will fail to create the directory where to temporarily
-store the compiled formats.
+This is very important, since <c>fmtutil</c> looks for <c>mktexdir</c>
+at this location; if you have a different result then <c>fmtutil</c>
+will not find <c>mktexdir</c> and thus will fail to create the
+directory where to temporarily store the compiled formats.
</p>
<p>
There is no magic command to fix this one, you should check that your
-configuration is correct, that there is no stray configuration file in
-<path>/etc/texmf/texmf.d</path>. This will most likely be due to
-<path>00texmf.cnf</path> being still there and thus setting wrong definitions
-for the <path>texmf.cnf</path> file. Please refer to the <uri
-link="#uninstall">Clean uninstall chapter </uri>.
+configuration is correct, that there are no stray configuration files
+in <path>/etc/texmf/texmf.d</path>. This will most likely be due to an
+old <path>00texmf.cnf</path> being still there and thus setting wrong
+definitions for the <path>texmf.cnf</path> file. Please refer to the
+<uri link="#uninstall">Clean uninstall chapter </uri>.
</p>
</body>
@@ -485,8 +497,8 @@
<body>
<p>
-When installing <c>texlive-latex</c> (or any other format that has babel
-hyphenation support), you might encounter an error like:
+When installing <c>texlive-latex</c> (or any other format that has
+babel hyphenation support), you might encounter an error like:
</p>
<pre caption="missing bghyphen.tex">
@@ -517,8 +529,8 @@
</pre>
<p>
-In that case, you will have to check which <path>language.dat</path> file is
-being used:
+In that case, you will have to check which <path>language.dat</path>
+file is being used:
</p>
<pre caption="find language.dat">
@@ -527,15 +539,16 @@
</pre>
<p>
-This file is automatically generated by <c>texmf-update</c>, it is the result of
-the concatenation of <path>language.*.dat</path> files present in the directory
-where is <path>language.us</path>. This directory should be
-<path>/usr/share/texmf/tex/generic/config/</path>. So you should check that
-there are no other <path>language.*.dat</path> files in that directory than the
-ones installed by the various <c>dev-texlive/texlive-lang*</c> ebuilds. A file
-present in that directory means that you want to enable hyphenation support for
-a specific language; and if you don't have the hyphenation support files this
-will cause formats that can use this extra hyphenation support to fail to build.
+This file is automatically generated by <c>texmf-update</c> and is the
+result of concatenating <path>language.*.dat</path> files present in
+the directory with <path>language.us</path>. This directory should be
+<path>/usr/share/texmf/tex/generic/config/</path>. So you should check
+that there are no other <path>language.*.dat</path> files in that
+directory other than the ones installed by the various
+<c>dev-texlive/texlive-lang*</c> ebuilds. A file present in that
+directory means that you want to enable hyphenation support for a
+specific language; if you don't have the hyphenation support files the
+formats that use this extra hyphenation support will fail to build.
</p>
</body>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml
@ 2008-03-09 12:41 Lukasz Damentko (rane)
0 siblings, 0 replies; 7+ messages in thread
From: Lukasz Damentko (rane) @ 2008-03-09 12:41 UTC (permalink / raw
To: gentoo-commits
rane 08/03/09 12:41:24
Modified: texlive-migration-guide.xml
Log:
cleaned up guidexml to fit to gdp standards, no content change
Revision Changes Path
1.2 xml/htdocs/proj/en/tex/texlive-migration-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.1&r2=1.2
Index: texlive-migration-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- texlive-migration-guide.xml 21 Dec 2007 00:10:29 -0000 1.1
+++ texlive-migration-guide.xml 9 Mar 2008 12:41:24 -0000 1.2
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.1 2007/12/21 00:10:29 aballier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.2 2008/03/09 12:41:24 rane Exp $ -->
-<guide lang="en">
+<guide link="/proj/en/tex/texlive-migration-guide.xml">
<title>TeX Live 2007 guide</title>
<author title="Author">
@@ -10,9 +10,9 @@
</author>
<abstract>
-This guide aims to show you how to install TeX Live 2007 on Gentoo, more specifically
-what you need to take care of if you already had a TeX distribution installed
-(like tetex or TeX Live 2005).
+This guide aims to show you how to install TeX Live 2007 on Gentoo, more
+specifically what you need to take care of if you already had a TeX distribution
+installed (like tetex or TeX Live 2005).
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -23,69 +23,79 @@
<date>2007-12-20</date>
<chapter id="uninstall">
-<title> Clean uninstall </title>
+<title>Clean uninstall</title>
<section>
<title>Introduction</title>
<body>
+
<p>
-In this section we will assume that you have <c> >=app-text/tetex-3 </c>
-installed. This applies as well if you had installed <c>app-text/texlive-2005</c>.
-In a perfect world it would be as simple as unmerging it, but unfortunately it is not.
+In this section we will assume that you have <c>>=app-text/tetex-3</c>
+installed. This applies as well if you had installed
+<c>app-text/texlive-2005</c>. In a perfect world it would be as simple as
+unmerging it, but unfortunately it is not.
</p>
+
</body>
</section>
-
<section>
<title>Saving your old configuration</title>
<body>
+
<p>
If you had modified your configuration of <c>tetex</c> by editing files in
-<path>/etc/texmf</path>,
-you should first save them:
+<path>/etc/texmf</path>, you should first save them:
</p>
+
<pre caption="Save your old configuration files">
$ <i>cp -rf /etc/texmf /tmp/tetex-texmf</i>
</pre>
+
</body>
</section>
<section>
<title>Removing tetex</title>
<body>
+
<p>
Then you can unmerge safely <c>tetex</c>:
</p>
+
<pre caption="Remove tetex">
# <i>emerge -C tetex</i>
</pre>
<p>
-Some weird errors have been reported when there were stray configuration files left
-in <path>/etc/texmf</path>. For safety and a clean install of <c>TeX Live</c> it is
-recommended to remove the <path>/etc/texmf/texmf.d/00texmf.cnf</path> file:
+Some weird errors have been reported when there were stray configuration files
+left in <path>/etc/texmf</path>. For safety and a clean install of <c>TeX
+Live</c> it is recommended to remove the
+<path>/etc/texmf/texmf.d/00texmf.cnf</path> file:
</p>
+
<pre caption="Cleanup /etc/texmf">
# <i>rm /etc/texmf/texmf.d/00texmf.cnf</i>
</pre>
-<note>
+
+<note>
You have not lost anything since you just saved your old configuration files.
</note>
-
<p>
Due to <c>tetex</c> using <c>texlinks</c> outside of the scope of the package
manager, simply unmerging it will have left some stray symlinks:
</p>
+
<pre caption="tetex stray symlink">
$ <i>ls -l /usr/bin/pdftex</i>
lrwxrwxrwx 1 root root 7 2007-07-09 07:34 /usr/bin/pdftex -> pdfetex
</pre>
+
<p>
Of course, pdfetex has gone with <c>tetex</c>'s removal, so the pdftex symlink
-is a dead one. It can be safely removed.
-The <c>find</c> command can help finding dead symlinks (with a GNU extension
-though):
+is a dead one. It can be safely removed. The <c>find</c> command can help
+finding dead symlinks (with a GNU extension though):
</p>
+
<pre caption="Find dead symlinks">
$ <i>find /usr/bin -type l ! -xtype f ! -xtype d</i>
@@ -99,6 +109,7 @@
/usr/bin/pdflatex
/usr/bin/pdfamstex
</pre>
+
<p>
These are the files left over by my <c>tetex</c> installation.
</p>
@@ -107,9 +118,10 @@
<c>tetex</c> was also using <c>fmtutil</c> outside of the scope of the package
manager to generate the format files. With <c>TeX Live 2007</c> we are now
building most of the format files while compiling the packages; which format
-files will be installed in <path>/var/lib/texmf</path>. That means you have to make
-sure that there are no stray format files:
+files will be installed in <path>/var/lib/texmf</path>. That means you have to
+make sure that there are no stray format files:
</p>
+
<pre caption="Remove stray format files">
# <i>rm -rf /var/lib/texmf/web2c</i>
</pre>
@@ -117,15 +129,17 @@
</body>
</section>
</chapter>
+
<chapter>
-<title> Installing TeX Live 2007 </title>
+<title>Installing TeX Live 2007</title>
<section>
<body>
<p>
-If you have passed through all the above steps, now installing <c>TeX Live
+If you have passed through all the above steps, now installing <c>TeX Live
2007</c> should be very easy.
</p>
+
<pre caption="Install TeX Live 2007">
# <i>emerge texlive</i>
</pre>
@@ -139,22 +153,23 @@
<p>
Nevertheless, it is possible that you get dependencies problems, errors while
-installing a package, etc. In that case, you are advised to file a bug on
+installing a package, etc. In that case, you are advised to file a bug on
<uri>https://bugs.gentoo.org</uri>. If you do file a bug, please include at
least the output of <c>texconfig conf</c> (run as the same user that failed to
install because some environment variables might be important) in addition to
the error; this output will most often be requested.
</p>
+
</body>
</section>
</chapter>
<chapter>
-<title> Configuration </title>
-
+<title>Configuration</title>
<section>
<title>Introduction</title>
<body>
+
<p>
As it was the case for <c>tetex-3</c>, <c>TeX Live</c> on <c>Gentoo</c> has its
three main configuration files splitted and handled by <c>texmf-update</c>.
@@ -163,23 +178,26 @@
not modify them directly because the changes will be lost the next time
<c>texmf-update</c> is ran.
</p>
+
</body>
</section>
-
<section>
<title> texmf.cnf </title>
<body>
+
<p>
-The <path>texmf.cnf</path> configuration file is the main configuration file for your
-TeX installation, it contains various variable definitions that will be used by
-a lot of programs.
+The <path>texmf.cnf</path> configuration file is the main configuration file for
+your TeX installation, it contains various variable definitions that will be
+used by a lot of programs.
</p>
+
<p>
-The <path>texmf.cnf</path> file is the result of the concatenation of the files in
-<path>/etc/texmf/texmf.d</path>. In order to modify your TeX environment
+The <path>texmf.cnf</path> file is the result of the concatenation of the files
+in <path>/etc/texmf/texmf.d</path>. In order to modify your TeX environment
configuration, you should modify the files there. At the time of writing,
<c>Gentoo TeX Live</c>'s ebuild install six files there:
</p>
+
<pre caption="texmf.d installed files">
00header.cnf
05searchpaths.cnf
@@ -188,6 +206,7 @@
20sizes.cnf
25misc.cnf
</pre>
+
<p>
This is the result of the splitting in their respective sections of a (lightly)
modified <path>texmf.cnf</path> file from <c>TeX Live 2007</c> DVD.
@@ -198,9 +217,10 @@
<path>10standardpaths.cnf</path> and <path>25misc.cnf</path> should not be
modified and kept as is. If the defaults can be improved, please file a bug.
</p>
+
<warn>
-The <c>TeX Live</c> ebuilds are not aware of paths changes of those files,
-so if you change any path there, make sure you know what you are doing.
+The <c>TeX Live</c> ebuilds are not aware of paths changes of those files, so if
+yuu change any path there, make sure you know what you are doing.
</warn>
<p>
@@ -212,39 +232,42 @@
</p>
<p>
-If you wish to append some additions to the <path>texmf.cnf</path> file, you can also
-create a new file in <path>/etc/texmf/texmf.d</path>, called for example
-<path>99myadditions.cnf</path>. Beware though to not give it a higher priority than
-the core configuration files, so it should begin with a two digits number greater than
-<c>25</c>.
+If you wish to append some additions to the <path>texmf.cnf</path> file, you can
+also create a new file in <path>/etc/texmf/texmf.d</path>, called for example
+<path>99myadditions.cnf</path>. Beware though to not give it a higher priority
+than the core configuration files, so it should begin with a two digits number
+greater than <c>25</c>.
</p>
<p>
-Packages that need to append something to the <path>texmf.cnf</path> file get the same
-treatment, they should install a <path>texmf.d</path> file instead:
+Packages that need to append something to the <path>texmf.cnf</path> file get
+the same treatment, they should install a <path>texmf.d</path> file instead:
</p>
+
<pre caption="Sample code for installing a texmf.d file">
<keyword>insinto</keyword> <const>/etc/texmf/texmf.d</const>
<keyword>doins</keyword> <const>40mytexmfadditions.cnf</const>
</pre>
+
</body>
</section>
-
<section>
<title>updmap.cfg</title>
<body>
+
<p>
-The <path>updmap.cfg</path> is the configuration file used by <c>updmap</c>
-(and <c>updmap-sys</c>), unless otherwise specified. It tells it which font maps
-to update for the various TeX output drivers.
+The <path>updmap.cfg</path> is the configuration file used by <c>updmap</c> (and
+<c>updmap-sys</c>), unless otherwise specified. It tells it which font maps to
+update for the various TeX output drivers.
</p>
+
<p>
-The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is the result of
-the concatenation of the files in <path>/etc/texmf/updmap.d</path>.
-The initial <path>00updmap.cfg</path> file installed by <c>app-text/texlive-core</c> is
-the result of <c>updmap --syncwithtrees</c> ran on the <c>texmf</c> tree that it
-installs (in fact, it just mimics what <c>updmap --syncwithtrees</c> would do,
-but it is only a technical detail).
+The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is the result
+of the concatenation of the files in <path>/etc/texmf/updmap.d</path>. The
+initial <path>00updmap.cfg</path> file installed by <c>app-text/texlive-core</c>
+is the result of <c>updmap --syncwithtrees</c> ran on the <c>texmf</c> tree that
+it installs (in fact, it just mimics what <c>updmap --syncwithtrees</c> would
+do, but it is only a technical detail).
</p>
<p>
@@ -258,17 +281,20 @@
If a third party package wants to add some font maps, it should install a file
in <path>/etc/texmf/updmap.d</path> and let <c>texmf-update</c> handle it.
</p>
+
<warn>
Sometimes you can see <c>updmap-sys --enable Map=mymap.map</c> in some ebuilds
or some installation instructions of a third party font package, while this
might work at a first try, the changes will be reverted the next time
<c>texmf-update</c> is ran.
</warn>
+
<p>
The good way of handling it would be to create a file to be installed in
-<path>/etc/texmf/updmap.d</path> and install it for TeX distributions that support the
-<c>texmf-update</c> way:
+<path>/etc/texmf/updmap.d</path> and install it for TeX distributions that
+support the <c>texmf-update</c> way:
</p>
+
<pre caption="How to enable a font map">
<keyword>inherit</keyword> <ident>latex-package</ident>
...
@@ -291,84 +317,95 @@
<stmt>latex-package_has_tetex_3</stmt> || updmap-sys --disable Map=mymap.map
}
</pre>
+
<p>
-The files in <path>/etc/texmf/updmap.d</path> should respect <c>updmap</c> syntax:
+The files in <path>/etc/texmf/updmap.d</path> should respect <c>updmap</c>
+syntax:
</p>
+
<pre caption="Snippet of updmap.cfg explaining the syntax">
There are two possible entries: Map and MixedMap. Both have one additional
-argument: the file name of the map file. MixedMap ("mixed" means that
-the font is available as bitmap and as outline) lines will not be used
-in the default map of dvips if dvipsPreferOutline is false. Inactive
-Map files should be marked by "#! " (without the quotes), not just #.
+argument: the file name of the map file. MixedMap ("mixed" means that the font
+is available as bitmap and as outline) lines will not be used in the default map
+of dvips if dvipsPreferOutline is false. Inactive Map files should be marked by
+"#! " (without the quotes), not just #.
</pre>
+
</body>
</section>
<section>
<title>fmtutil.cnf</title>
<body>
+
<p>
-The <path>fmtutil.cnf</path> file contains the information on how to build a format
-file and how to handle it.
+The <path>fmtutil.cnf</path> file contains the information on how to build a
+format file and how to handle it.
</p>
<p>
-The <path>fmtutil.cnf</path> file is the result of the concatenation of the files in
-<path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c> ebuilds install files
-there, those files come with the formats they add support for and the symlink to
-the relevant engine.
+The <path>fmtutil.cnf</path> file is the result of the concatenation of the
+files in <path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c> ebuilds
+install files there, those files come with the formats they add support for and
+the symlink to the relevant engine.
</p>
<pre caption="Snippet of the fmtutil.cnf(5) man page that explains the syntax">
The fmtutil.cnf file contains the configuration information for fmtutil(8).
-Each line contains the name of the format (e.g., "tex", "latex", "omega"),
-the name of the engine that is used by that format (e.g., "tex", "etex", "omega"),
-the pattern file (e.g., language.dat, language.def), and any arguments
-(name of an .ini file).
-
-Fields are separated by whitespace and complete lines can be commented out with "#".
-The "pattern file" field cannot be used to define a file that is used while
-building the format. It tells fmtutil which file the format creation procedure reads
-and it has an effect to the options --showhyphen and --byhyphen.
-If the format has no way to customize hyphenation, a "-" can be used to indicate this.
+Each line contains the name of the format (e.g., "tex", "latex", "omega"), the
+name of the engine that is used by that format (e.g., "tex", "etex", "omega"),
+the pattern file (e.g., language.dat, language.def), and any arguments (name of
+an .ini file).
+
+Fields are separated by whitespace and complete lines can be commented out with
+"#". The "pattern file" field cannot be used to define a file that is used
+while building the format. It tells fmtutil which file the format creation
+procedure reads and it has an effect to the options --showhyphen and --byhyphen.
+If the format has no way to customize hyphenation, a "-" can be used to indicate
+this.
</pre>
+
<p>
-<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file install the relevant
-format files in <path>/var/lib/texmf/web2c</path> and create the symlink from the format to
-the engine.
+<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file install the
+relevant format files in <path>/var/lib/texmf/web2c</path> and create the
+symlink from the format to the engine.
</p>
+
<p>
It should be noted that when a support file for a language gets added,
-<c>texmf-update</c> takes care of adding it to the <path>language.dat</path> file and
-regenerates the format files so that they support the newly installed language.
+<c>texmf-update</c> takes care of adding it to the <path>language.dat</path>
+file and regenerates the format files so that they support the newly installed
+language.
</p>
+
</body>
</section>
<section>
-<title> Updating your configuration </title>
+<title>Updating your configuration</title>
<body>
+
<p>
-Now that you know how <c>TeX Live</c> configuration is managed, you should
-be able to port the changes you had made to your older TeX distribution
+Now that you know how <c>TeX Live</c> configuration is managed, you should be
+able to port the changes you had made to your older TeX distribution
configuration to the <c>TeX Live</c> configuration layout.
</p>
+
</body>
</section>
-
</chapter>
<chapter>
-<title> Common errors </title>
-
+<title>Common errors</title>
<section>
<title>Introduction</title>
<body>
+
<p>
In this chapter we will try to give a short summary of the most common errors
and explain what has gone wrong.
</p>
+
</body>
</section>
-
<section>
<title>Format was written by (pdf)etex</title>
<body>
@@ -377,27 +414,30 @@
Sometimes when installing some packages that requires latex, you'll get this
error:
</p>
+
<pre caption="Format was written by pdfetex">
---! //var/lib/texmf/web2c/latex.fmt was written by pdfetex
</pre>
+
<p>
This is due to old files remaining from an old installation of a <c>TeX</c>
distribution based on <c>etex</c>. That most likely means you did not follow
entirely this guide, especially the <uri link="#uninstall">Clean uninstall
-chapter </uri>.
+chapter</uri>.
</p>
<p>
Nevertheless, it is still possible to fix it quickly without having to reinstall
anything, just run as root:
</p>
+
<pre caption="Remove old formats">
# <i>rm -rf /var/lib/texmf/web2c</i>
# <i>texmf-update</i>
</pre>
+
</body>
</section>
-
<section>
<title>Format directory does not exist</title>
<body>
@@ -405,6 +445,7 @@
<p>
When installing e.g., <c>texlive-latex</c>, you might encounter the error:
</p>
+
<pre caption="Format directory does not exist">
fmtutil: format directory
`/var/tmp/portage/dev-texlive/texlive-latex-2007/work/texmf-var/web2c' does not
@@ -415,10 +456,12 @@
This is most likely to be due to a wrong configuration. You should try to run
the following command and get the same results:
</p>
+
<pre caption="TEXMFMAIN definition">
$ <i>kpsewhich --var-value=TEXMFMAIN</i>
/usr/share/texmf
</pre>
+
<p>
This is very important, since <c>fmtutil</c> looks for <c>mktexdir</c> at this
location; if you have a different result then <c>fmtutil</c> will not find
@@ -434,16 +477,18 @@
for the <path>texmf.cnf</path> file. Please refer to the <uri
link="#uninstall">Clean uninstall chapter </uri>.
</p>
+
</body>
</section>
-
<section>
<title>Missing .tex files</title>
<body>
+
<p>
When installing <c>texlive-latex</c> (or any other format that has babel
hyphenation support), you might encounter an error like:
</p>
+
<pre caption="missing bghyphen.tex">
===========================================
Local configuration file hyphen.cfg used
@@ -461,7 +506,7 @@
! I can't find file `bghyphen.tex'.
l.10 \input bghyphen.tex
-Please type another input file name:
+Please type another input file name:
! Emergency stop.
l.10 \input bghyphen.tex
@@ -470,25 +515,29 @@
Error: `pdftex -ini -jobname=latex -progname=latex
-translate-file=cp227.tcx *latex.ini' failed
</pre>
+
<p>
-In that case, you will have to check which <path>language.dat</path> file is being
-used:
+In that case, you will have to check which <path>language.dat</path> file is
+being used:
</p>
+
<pre caption="find language.dat">
$ <i>kpsewhich language.dat</i>
/usr/share/texmf/tex/generic/config/language.dat
</pre>
+
<p>
This file is automatically generated by <c>texmf-update</c>, it is the result of
-the concatenation of <path>language.*.dat</path> files present in the directory where
-is <path>language.us</path>. This directory should be
-<path>/usr/share/texmf/tex/generic/config/</path>. So you should check that there are
-no other <path>language.*.dat</path> files in that directory than the ones installed
-by the various <c>dev-texlive/texlive-lang*</c> ebuilds. A file present in that
-directory means that you want to enable hyphenation support for a specific
-language; and if you don't have the hyphenation support files this will cause
-formats that can use this extra hyphenation support to fail to build.
+the concatenation of <path>language.*.dat</path> files present in the directory
+where is <path>language.us</path>. This directory should be
+<path>/usr/share/texmf/tex/generic/config/</path>. So you should check that
+there are no other <path>language.*.dat</path> files in that directory than the
+ones installed by the various <c>dev-texlive/texlive-lang*</c> ebuilds. A file
+present in that directory means that you want to enable hyphenation support for
+a specific language; and if you don't have the hyphenation support files this
+will cause formats that can use this extra hyphenation support to fail to build.
</p>
+
</body>
</section>
</chapter>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-10-28 15:29 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-28 15:21 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/tex: texlive-migration-guide.xml Sven Vermeulen (swift)
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 5:59 Alexis Ballier (aballier)
2009-04-03 23:04 Christian Faulhammer (fauli)
2008-11-14 9:54 Alexis Ballier (aballier)
2008-09-30 21:00 Alexis Ballier (aballier)
2008-03-30 10:33 Alexis Ballier (aballier)
2008-03-09 12:41 Lukasz Damentko (rane)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox