1 |
aballier 08/03/30 10:33:30 |
2 |
|
3 |
Modified: texlive-migration-guide.xml |
4 |
Log: |
5 |
Update by John Christian Stoddart: grammar and simpler way of removing dead symlinks. |
6 |
|
7 |
Revision Changes Path |
8 |
1.3 xml/htdocs/proj/en/tex/texlive-migration-guide.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.3&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?rev=1.3&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml?r1=1.2&r2=1.3 |
13 |
|
14 |
Index: texlive-migration-guide.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v |
17 |
retrieving revision 1.2 |
18 |
retrieving revision 1.3 |
19 |
diff -u -r1.2 -r1.3 |
20 |
--- texlive-migration-guide.xml 9 Mar 2008 12:41:24 -0000 1.2 |
21 |
+++ texlive-migration-guide.xml 30 Mar 2008 10:33:30 -0000 1.3 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.2 2008/03/09 12:41:24 rane Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/tex/texlive-migration-guide.xml,v 1.3 2008/03/30 10:33:30 aballier Exp $ --> |
27 |
|
28 |
<guide link="/proj/en/tex/texlive-migration-guide.xml"> |
29 |
<title>TeX Live 2007 guide</title> |
30 |
@@ -10,17 +10,17 @@ |
31 |
</author> |
32 |
|
33 |
<abstract> |
34 |
-This guide aims to show you how to install TeX Live 2007 on Gentoo, more |
35 |
-specifically what you need to take care of if you already had a TeX distribution |
36 |
-installed (like tetex or TeX Live 2005). |
37 |
+This guide aims to show you how to install TeX Live 2007 on Gentoo, |
38 |
+more specifically what you need to take care of if you already have a |
39 |
+TeX distribution installed (like tetex or TeX Live 2005). |
40 |
</abstract> |
41 |
|
42 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
43 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
44 |
<license/> |
45 |
|
46 |
-<version>1.0</version> |
47 |
-<date>2007-12-20</date> |
48 |
+<version>1.1</version> |
49 |
+<date>2008-03-30</date> |
50 |
|
51 |
<chapter id="uninstall"> |
52 |
<title>Clean uninstall</title> |
53 |
@@ -31,9 +31,9 @@ |
54 |
|
55 |
<p> |
56 |
In this section we will assume that you have <c>>=app-text/tetex-3</c> |
57 |
-installed. This applies as well if you had installed |
58 |
-<c>app-text/texlive-2005</c>. In a perfect world it would be as simple as |
59 |
-unmerging it, but unfortunately it is not. |
60 |
+installed. This also applies if you had <c>app-text/texlive-2005</c> |
61 |
+installed. In a perfect world it would be as simple as unmerging it, |
62 |
+but unfortunately it is not. |
63 |
</p> |
64 |
|
65 |
</body> |
66 |
@@ -43,8 +43,8 @@ |
67 |
<body> |
68 |
|
69 |
<p> |
70 |
-If you had modified your configuration of <c>tetex</c> by editing files in |
71 |
-<path>/etc/texmf</path>, you should first save them: |
72 |
+If you have modified your configuration of <c>tetex</c> editing the |
73 |
+files in <path>/etc/texmf</path>, you should save them first: |
74 |
</p> |
75 |
|
76 |
<pre caption="Save your old configuration files"> |
77 |
@@ -58,7 +58,7 @@ |
78 |
<body> |
79 |
|
80 |
<p> |
81 |
-Then you can unmerge safely <c>tetex</c>: |
82 |
+Now you can safely unmerge <c>tetex</c>: |
83 |
</p> |
84 |
|
85 |
<pre caption="Remove tetex"> |
86 |
@@ -66,9 +66,9 @@ |
87 |
</pre> |
88 |
|
89 |
<p> |
90 |
-Some weird errors have been reported when there were stray configuration files |
91 |
-left in <path>/etc/texmf</path>. For safety and a clean install of <c>TeX |
92 |
-Live</c> it is recommended to remove the |
93 |
+Some weird errors have been reported when stray configuration files |
94 |
+were left behind in <path>/etc/texmf</path>. For safety and for a |
95 |
+clean install of <c>TeX Live</c> it is recommended to remove the |
96 |
<path>/etc/texmf/texmf.d/00texmf.cnf</path> file: |
97 |
</p> |
98 |
|
99 |
@@ -81,8 +81,9 @@ |
100 |
</note> |
101 |
|
102 |
<p> |
103 |
-Due to <c>tetex</c> using <c>texlinks</c> outside of the scope of the package |
104 |
-manager, simply unmerging it will have left some stray symlinks: |
105 |
+Due to <c>tetex</c> using <c>texlinks</c> outside of the scope of the |
106 |
+package manager, simply unmerging it will have left behind some stray |
107 |
+symlinks: |
108 |
</p> |
109 |
|
110 |
<pre caption="tetex stray symlink"> |
111 |
@@ -92,32 +93,34 @@ |
112 |
|
113 |
<p> |
114 |
Of course, pdfetex has gone with <c>tetex</c>'s removal, so the pdftex symlink |
115 |
-is a dead one. It can be safely removed. The <c>find</c> command can help |
116 |
-finding dead symlinks (with a GNU extension though): |
117 |
+is dead and can be safely removed. The <c>find</c> command (with a GNU |
118 |
+extension though) can help us find and remove dead symlinks interactively: |
119 |
</p> |
120 |
|
121 |
-<pre caption="Find dead symlinks"> |
122 |
-$ <i>find /usr/bin -type l ! -xtype f ! -xtype d</i> |
123 |
+<pre caption="Eliminate dead symlinks interactively"> |
124 |
+# <i>find /usr/bin -type l ! -xtype f ! -xtype d -ok rm -f {} \;</i> |
125 |
|
126 |
-/usr/bin/lamed |
127 |
-/usr/bin/latex |
128 |
-/usr/bin/amstex |
129 |
-/usr/bin/elatex |
130 |
-/usr/bin/eplain |
131 |
-/usr/bin/lambda |
132 |
-/usr/bin/pdftex |
133 |
-/usr/bin/pdflatex |
134 |
-/usr/bin/pdfamstex |
135 |
+< rm ... /usr/bin/pdflatex > ? y |
136 |
+< rm ... /usr/bin/amstex > ? y |
137 |
+< rm ... /usr/bin/pdftex > ? y |
138 |
+< rm ... /usr/bin/eplain > ? y |
139 |
+< rm ... /usr/bin/jadetex > ? y |
140 |
+< rm ... /usr/bin/lambda > ? y |
141 |
+< rm ... /usr/bin/pdfamstex > ? y |
142 |
+< rm ... /usr/bin/elatex > ? y |
143 |
+< rm ... /usr/bin/lamed > ? y |
144 |
+< rm ... /usr/bin/pdfjadetex > ? y |
145 |
+< rm ... /usr/bin/latex > ? y |
146 |
</pre> |
147 |
|
148 |
<p> |
149 |
-These are the files left over by my <c>tetex</c> installation. |
150 |
+These were the files left over by my <c>tetex</c> installation. |
151 |
</p> |
152 |
|
153 |
<p> |
154 |
<c>tetex</c> was also using <c>fmtutil</c> outside of the scope of the package |
155 |
-manager to generate the format files. With <c>TeX Live 2007</c> we are now |
156 |
-building most of the format files while compiling the packages; which format |
157 |
+manager to generate the format files. With <c>TeX Live 2007</c> we now |
158 |
+build most of the format files while compiling the packages; which format |
159 |
files will be installed in <path>/var/lib/texmf</path>. That means you have to |
160 |
make sure that there are no stray format files: |
161 |
</p> |
162 |
@@ -136,8 +139,8 @@ |
163 |
<body> |
164 |
|
165 |
<p> |
166 |
-If you have passed through all the above steps, now installing <c>TeX Live |
167 |
-2007</c> should be very easy. |
168 |
+If you have passed through all the above steps, installing <c>TeX Live |
169 |
+2007</c> now should be very easy. |
170 |
</p> |
171 |
|
172 |
<pre caption="Install TeX Live 2007"> |
173 |
@@ -145,19 +148,20 @@ |
174 |
</pre> |
175 |
|
176 |
<p> |
177 |
-In theory this should just go smoothly and install everything. You might want at |
178 |
-some point to tune <c>app-text/texlive</c> use flags to install extra TeX |
179 |
-packages, but you can do it later; <c>app-text/texlive</c> is just a meta-ebuild |
180 |
-that pulls the real packages depending on its use flags. |
181 |
+In theory this should just go smoothly and install everything. You |
182 |
+might want to tune <c>app-text/texlive</c> USE flags to install extra |
183 |
+TeX packages, but you can do it later; <c>app-text/texlive</c> is just |
184 |
+a meta-ebuild that pulls the real packages depending on its USE flags. |
185 |
</p> |
186 |
|
187 |
<p> |
188 |
-Nevertheless, it is possible that you get dependencies problems, errors while |
189 |
-installing a package, etc. In that case, you are advised to file a bug on |
190 |
-<uri>https://bugs.gentoo.org</uri>. If you do file a bug, please include at |
191 |
-least the output of <c>texconfig conf</c> (run as the same user that failed to |
192 |
-install because some environment variables might be important) in addition to |
193 |
-the error; this output will most often be requested. |
194 |
+Nevertheless, it is possible to get dependency problems, errors while |
195 |
+installing a package, etc. In that case, you are advised to file a bug |
196 |
+on <uri>https://bugs.gentoo.org</uri>. If you file a bug, please |
197 |
+include at least the output of <c>texconfig conf</c> (run as the same |
198 |
+user that failed to install, because some environment variables might |
199 |
+be important) in addition to the error; this output will most often be |
200 |
+requested. |
201 |
</p> |
202 |
|
203 |
</body> |
204 |
@@ -171,12 +175,12 @@ |
205 |
<body> |
206 |
|
207 |
<p> |
208 |
-As it was the case for <c>tetex-3</c>, <c>TeX Live</c> on <c>Gentoo</c> has its |
209 |
-three main configuration files splitted and handled by <c>texmf-update</c>. |
210 |
+As was the case for <c>tetex-3</c>, <c>TeX Live</c> on <c>Gentoo</c> has its |
211 |
+three main configuration files separated and handled by <c>texmf-update</c>. |
212 |
These files are, namely, <path>texmf.cnf</path>, <path>fmtutil.cnf</path>, |
213 |
<path>updmap.cfg</path>. They lie in <path>/etc/texmf/web2c</path>; you should |
214 |
not modify them directly because the changes will be lost the next time |
215 |
-<c>texmf-update</c> is ran. |
216 |
+<c>texmf-update</c> is run. |
217 |
</p> |
218 |
|
219 |
</body> |
220 |
@@ -186,13 +190,13 @@ |
221 |
<body> |
222 |
|
223 |
<p> |
224 |
-The <path>texmf.cnf</path> configuration file is the main configuration file for |
225 |
-your TeX installation, it contains various variable definitions that will be |
226 |
-used by a lot of programs. |
227 |
+The <path>texmf.cnf</path> file is the main TeX installation |
228 |
+configuration file. It contains variable definitions that will be used |
229 |
+by a lot of programs. |
230 |
</p> |
231 |
|
232 |
<p> |
233 |
-The <path>texmf.cnf</path> file is the result of the concatenation of the files |
234 |
+The <path>texmf.cnf</path> file is the result of concatenating files |
235 |
in <path>/etc/texmf/texmf.d</path>. In order to modify your TeX environment |
236 |
configuration, you should modify the files there. At the time of writing, |
237 |
<c>Gentoo TeX Live</c>'s ebuild install six files there: |
238 |
@@ -208,40 +212,44 @@ |
239 |
</pre> |
240 |
|
241 |
<p> |
242 |
-This is the result of the splitting in their respective sections of a (lightly) |
243 |
-modified <path>texmf.cnf</path> file from <c>TeX Live 2007</c> DVD. |
244 |
+This is the result of the splitting in their respective sections of a |
245 |
+(lightly) modified <path>texmf.cnf</path> file from <c>TeX Live |
246 |
+2007</c> DVD. |
247 |
</p> |
248 |
|
249 |
<p> |
250 |
-The files <path>00header.cnf</path>, <path>05searchpaths.cnf</path>, |
251 |
-<path>10standardpaths.cnf</path> and <path>25misc.cnf</path> should not be |
252 |
-modified and kept as is. If the defaults can be improved, please file a bug. |
253 |
+The <path>00header.cnf</path>, <path>05searchpaths.cnf</path>, |
254 |
+<path>10standardpaths.cnf</path> and <path>25misc.cnf</path> files |
255 |
+should not be modified. If the defaults can be improved, please file a |
256 |
+bug. |
257 |
</p> |
258 |
|
259 |
<warn> |
260 |
-The <c>TeX Live</c> ebuilds are not aware of paths changes of those files, so if |
261 |
-yuu change any path there, make sure you know what you are doing. |
262 |
+The <c>TeX Live</c> ebuilds are not aware of path changes of those |
263 |
+files, so if you change any path there, make sure you know what you |
264 |
+are doing. |
265 |
</warn> |
266 |
|
267 |
<p> |
268 |
-The files <path>15options.cnf</path> and <path>20sizes.cnf</path> can be |
269 |
-modified with caution. The comments in these files should be explicit of what |
270 |
-option means what. For example, in <path>20sizes.cnf</path> you can increase TeX |
271 |
-memory, in case you are trying to compile a too big document and run into <c>TeX |
272 |
-capacity exceeded, sorry</c> errors. |
273 |
+The <path>15options.cnf</path> and <path>20sizes.cnf</path> files can |
274 |
+be modified with caution. The comments in these files should explain |
275 |
+what options mean. For example, in <path>20sizes.cnf</path> you can |
276 |
+increase TeX memory, in case you are trying to compile a document that |
277 |
+is too big and runs into <c>TeX capacity exceeded, sorry</c> errors. |
278 |
</p> |
279 |
|
280 |
<p> |
281 |
-If you wish to append some additions to the <path>texmf.cnf</path> file, you can |
282 |
-also create a new file in <path>/etc/texmf/texmf.d</path>, called for example |
283 |
-<path>99myadditions.cnf</path>. Beware though to not give it a higher priority |
284 |
-than the core configuration files, so it should begin with a two digits number |
285 |
-greater than <c>25</c>. |
286 |
+If you wish to append additions to the <path>texmf.cnf</path> file, |
287 |
+you can also create a new file in <path>/etc/texmf/texmf.d</path>, |
288 |
+called for example <path>99myadditions.cnf</path>. Beware not to give |
289 |
+it a higher priority than the core configuration files, so it should |
290 |
+begin with a two digit number greater than <c>25</c>. |
291 |
</p> |
292 |
|
293 |
<p> |
294 |
-Packages that need to append something to the <path>texmf.cnf</path> file get |
295 |
-the same treatment, they should install a <path>texmf.d</path> file instead: |
296 |
+Packages that need to append something to the <path>texmf.cnf</path> |
297 |
+file get the same treatment, they should install a |
298 |
+<path>texmf.d</path> file instead: |
299 |
</p> |
300 |
|
301 |
<pre caption="Sample code for installing a texmf.d file"> |
302 |
@@ -256,43 +264,46 @@ |
303 |
<body> |
304 |
|
305 |
<p> |
306 |
-The <path>updmap.cfg</path> is the configuration file used by <c>updmap</c> (and |
307 |
-<c>updmap-sys</c>), unless otherwise specified. It tells it which font maps to |
308 |
-update for the various TeX output drivers. |
309 |
+The <path>updmap.cfg</path> file is the configuration file used by |
310 |
+<c>updmap</c> (and <c>updmap-sys</c>), unless otherwise specified. It |
311 |
+tells it which font maps to update for the various TeX output drivers. |
312 |
</p> |
313 |
|
314 |
<p> |
315 |
-The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is the result |
316 |
-of the concatenation of the files in <path>/etc/texmf/updmap.d</path>. The |
317 |
-initial <path>00updmap.cfg</path> file installed by <c>app-text/texlive-core</c> |
318 |
-is the result of <c>updmap --syncwithtrees</c> ran on the <c>texmf</c> tree that |
319 |
-it installs (in fact, it just mimics what <c>updmap --syncwithtrees</c> would |
320 |
-do, but it is only a technical detail). |
321 |
+The <path>updmap.cfg</path> file in <path>/etc/texmf/web2c</path> is |
322 |
+the result of concatenating the files in |
323 |
+<path>/etc/texmf/updmap.d</path>. The initial |
324 |
+<path>00updmap.cfg</path> file installed by |
325 |
+<c>app-text/texlive-core</c> is the result of running <c>updmap |
326 |
+--syncwithtrees</c> on the the installed <c>texmf</c> tree (in fact, |
327 |
+it just mimics what <c>updmap --syncwithtrees</c> would do, but it is |
328 |
+only a technical detail). |
329 |
</p> |
330 |
|
331 |
<p> |
332 |
Various <c>TeX Live</c> ebuilds will add files to the |
333 |
-<path>/etc/texmf/updmap.d</path> directory, when they install fonts. While you |
334 |
-can edit those files to disable some font maps to be updated, it would probably |
335 |
-be wiser to remove the relevant package. |
336 |
+<path>/etc/texmf/updmap.d</path> directory when they install |
337 |
+fonts. While you can edit those files to disable some font maps to be |
338 |
+updated, it would probably be wiser to remove the relevant package. |
339 |
</p> |
340 |
|
341 |
<p> |
342 |
-If a third party package wants to add some font maps, it should install a file |
343 |
-in <path>/etc/texmf/updmap.d</path> and let <c>texmf-update</c> handle it. |
344 |
+If a third party package wants to add font maps, it should |
345 |
+install a file in <path>/etc/texmf/updmap.d</path> and let |
346 |
+<c>texmf-update</c> handle it. |
347 |
</p> |
348 |
|
349 |
<warn> |
350 |
-Sometimes you can see <c>updmap-sys --enable Map=mymap.map</c> in some ebuilds |
351 |
-or some installation instructions of a third party font package, while this |
352 |
-might work at a first try, the changes will be reverted the next time |
353 |
-<c>texmf-update</c> is ran. |
354 |
+Sometimes you can see <c>updmap-sys --enable Map=mymap.map</c> in some |
355 |
+ebuilds or some installation instructions of a third party font |
356 |
+package, while this might work at first, these changes will be |
357 |
+reverted the next time <c>texmf-update</c> is run. |
358 |
</warn> |
359 |
|
360 |
<p> |
361 |
-The good way of handling it would be to create a file to be installed in |
362 |
-<path>/etc/texmf/updmap.d</path> and install it for TeX distributions that |
363 |
-support the <c>texmf-update</c> way: |
364 |
+A better way of handling this would be to create a file to be |
365 |
+installed in <path>/etc/texmf/updmap.d</path> and install it for TeX |
366 |
+distributions that support the <c>texmf-update</c> way: |
367 |
</p> |
368 |
|
369 |
<pre caption="How to enable a font map"> |
370 |
@@ -338,15 +349,15 @@ |
371 |
<body> |
372 |
|
373 |
<p> |
374 |
-The <path>fmtutil.cnf</path> file contains the information on how to build a |
375 |
-format file and how to handle it. |
376 |
+The <path>fmtutil.cnf</path> file contains information on how to |
377 |
+build and handle a format file. |
378 |
</p> |
379 |
|
380 |
<p> |
381 |
-The <path>fmtutil.cnf</path> file is the result of the concatenation of the |
382 |
-files in <path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c> ebuilds |
383 |
-install files there, those files come with the formats they add support for and |
384 |
-the symlink to the relevant engine. |
385 |
+The <path>fmtutil.cnf</path> file is the result of concatenating the |
386 |
+files in <path>/etc/texmf/fmtutil.d</path>. Various <c>TeX Live</c> |
387 |
+ebuilds install files there. Those files come with the formats they |
388 |
+add support for and the symlink to the relevant engine. |
389 |
</p> |
390 |
|
391 |
<pre caption="Snippet of the fmtutil.cnf(5) man page that explains the syntax"> |
392 |
@@ -365,16 +376,16 @@ |
393 |
</pre> |
394 |
|
395 |
<p> |
396 |
-<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file install the |
397 |
-relevant format files in <path>/var/lib/texmf/web2c</path> and create the |
398 |
-symlink from the format to the engine. |
399 |
+<c>TeX Live</c> ebuilds that install a <path>fmtutil.d</path> file, |
400 |
+install the relevant format files in <path>/var/lib/texmf/web2c</path> |
401 |
+and create the symlink from the format to the engine. |
402 |
</p> |
403 |
|
404 |
<p> |
405 |
-It should be noted that when a support file for a language gets added, |
406 |
-<c>texmf-update</c> takes care of adding it to the <path>language.dat</path> |
407 |
-file and regenerates the format files so that they support the newly installed |
408 |
-language. |
409 |
+Note that when a support file for a language gets added, |
410 |
+<c>texmf-update</c> takes care of adding it to the |
411 |
+<path>language.dat</path> file and regenerates the format files to |
412 |
+support the newly installed language. |
413 |
</p> |
414 |
|
415 |
</body> |
416 |
@@ -384,9 +395,10 @@ |
417 |
<body> |
418 |
|
419 |
<p> |
420 |
-Now that you know how <c>TeX Live</c> configuration is managed, you should be |
421 |
-able to port the changes you had made to your older TeX distribution |
422 |
-configuration to the <c>TeX Live</c> configuration layout. |
423 |
+Now that you know how <c>TeX Live</c> configuration is managed, you |
424 |
+should be able to port the changes you had made to your older TeX |
425 |
+distribution configuration to the <c>TeX Live</c> configuration |
426 |
+layout. |
427 |
</p> |
428 |
|
429 |
</body> |
430 |
@@ -400,8 +412,8 @@ |
431 |
<body> |
432 |
|
433 |
<p> |
434 |
-In this chapter we will try to give a short summary of the most common errors |
435 |
-and explain what has gone wrong. |
436 |
+In this chapter we will try to give a short summary of the most common |
437 |
+errors and explain what has gone wrong. |
438 |
</p> |
439 |
|
440 |
</body> |
441 |
@@ -411,8 +423,8 @@ |
442 |
<body> |
443 |
|
444 |
<p> |
445 |
-Sometimes when installing some packages that requires latex, you'll get this |
446 |
-error: |
447 |
+Sometimes when installing some packages that requires latex, you'll |
448 |
+get this error: |
449 |
</p> |
450 |
|
451 |
<pre caption="Format was written by pdfetex"> |
452 |
@@ -421,14 +433,14 @@ |
453 |
|
454 |
<p> |
455 |
This is due to old files remaining from an old installation of a <c>TeX</c> |
456 |
-distribution based on <c>etex</c>. That most likely means you did not follow |
457 |
+distribution based on <c>etex</c>. This most likely means you did not follow |
458 |
entirely this guide, especially the <uri link="#uninstall">Clean uninstall |
459 |
chapter</uri>. |
460 |
</p> |
461 |
|
462 |
<p> |
463 |
-Nevertheless, it is still possible to fix it quickly without having to reinstall |
464 |
-anything, just run as root: |
465 |
+Nevertheless, it is still possible to fix it quickly without having to |
466 |
+reinstall anything, just run as root: |
467 |
</p> |
468 |
|
469 |
<pre caption="Remove old formats"> |
470 |
@@ -453,8 +465,8 @@ |
471 |
</pre> |
472 |
|
473 |
<p> |
474 |
-This is most likely to be due to a wrong configuration. You should try to run |
475 |
-the following command and get the same results: |
476 |
+This is most likely due to a wrong configuration. Try to run the |
477 |
+following command and get the same results: |
478 |
</p> |
479 |
|
480 |
<pre caption="TEXMFMAIN definition"> |
481 |
@@ -463,19 +475,19 @@ |
482 |
</pre> |
483 |
|
484 |
<p> |
485 |
-This is very important, since <c>fmtutil</c> looks for <c>mktexdir</c> at this |
486 |
-location; if you have a different result then <c>fmtutil</c> will not find |
487 |
-<c>mktexdir</c> and thus will fail to create the directory where to temporarily |
488 |
-store the compiled formats. |
489 |
+This is very important, since <c>fmtutil</c> looks for <c>mktexdir</c> |
490 |
+at this location; if you have a different result then <c>fmtutil</c> |
491 |
+will not find <c>mktexdir</c> and thus will fail to create the |
492 |
+directory where to temporarily store the compiled formats. |
493 |
</p> |
494 |
|
495 |
<p> |
496 |
There is no magic command to fix this one, you should check that your |
497 |
-configuration is correct, that there is no stray configuration file in |
498 |
-<path>/etc/texmf/texmf.d</path>. This will most likely be due to |
499 |
-<path>00texmf.cnf</path> being still there and thus setting wrong definitions |
500 |
-for the <path>texmf.cnf</path> file. Please refer to the <uri |
501 |
-link="#uninstall">Clean uninstall chapter </uri>. |
502 |
+configuration is correct, that there are no stray configuration files |
503 |
+in <path>/etc/texmf/texmf.d</path>. This will most likely be due to an |
504 |
+old <path>00texmf.cnf</path> being still there and thus setting wrong |
505 |
+definitions for the <path>texmf.cnf</path> file. Please refer to the |
506 |
+<uri link="#uninstall">Clean uninstall chapter </uri>. |
507 |
</p> |
508 |
|
509 |
</body> |
510 |
@@ -485,8 +497,8 @@ |
511 |
<body> |
512 |
|
513 |
<p> |
514 |
-When installing <c>texlive-latex</c> (or any other format that has babel |
515 |
-hyphenation support), you might encounter an error like: |
516 |
+When installing <c>texlive-latex</c> (or any other format that has |
517 |
+babel hyphenation support), you might encounter an error like: |
518 |
</p> |
519 |
|
520 |
<pre caption="missing bghyphen.tex"> |
521 |
@@ -517,8 +529,8 @@ |
522 |
</pre> |
523 |
|
524 |
<p> |
525 |
-In that case, you will have to check which <path>language.dat</path> file is |
526 |
-being used: |
527 |
+In that case, you will have to check which <path>language.dat</path> |
528 |
+file is being used: |
529 |
</p> |
530 |
|
531 |
<pre caption="find language.dat"> |
532 |
@@ -527,15 +539,16 @@ |
533 |
</pre> |
534 |
|
535 |
<p> |
536 |
-This file is automatically generated by <c>texmf-update</c>, it is the result of |
537 |
-the concatenation of <path>language.*.dat</path> files present in the directory |
538 |
-where is <path>language.us</path>. This directory should be |
539 |
-<path>/usr/share/texmf/tex/generic/config/</path>. So you should check that |
540 |
-there are no other <path>language.*.dat</path> files in that directory than the |
541 |
-ones installed by the various <c>dev-texlive/texlive-lang*</c> ebuilds. A file |
542 |
-present in that directory means that you want to enable hyphenation support for |
543 |
-a specific language; and if you don't have the hyphenation support files this |
544 |
-will cause formats that can use this extra hyphenation support to fail to build. |
545 |
+This file is automatically generated by <c>texmf-update</c> and is the |
546 |
+result of concatenating <path>language.*.dat</path> files present in |
547 |
+the directory with <path>language.us</path>. This directory should be |
548 |
+<path>/usr/share/texmf/tex/generic/config/</path>. So you should check |
549 |
+that there are no other <path>language.*.dat</path> files in that |
550 |
+directory other than the ones installed by the various |
551 |
+<c>dev-texlive/texlive-lang*</c> ebuilds. A file present in that |
552 |
+directory means that you want to enable hyphenation support for a |
553 |
+specific language; if you don't have the hyphenation support files the |
554 |
+formats that use this extra hyphenation support will fail to build. |
555 |
</p> |
556 |
|
557 |
</body> |
558 |
|
559 |
|
560 |
|
561 |
-- |
562 |
gentoo-commits@l.g.o mailing list |