summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html84
1 files changed, 0 insertions, 84 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html
deleted file mode 100644
index a09dc55989a..00000000000
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html
+++ /dev/null
@@ -1,84 +0,0 @@
-<head>
-<title>UK TeX FAQ -- question label what-TDS</title>
-</head><body>
-<h3>Which tree to use</h3>
-<p/>In almost all cases, new material that you install should go into the
-&#8220;local&#8221; tree of your (La)TeX installation. (A discussion of
-reasons <em>not</em> to use the local tree appears below.)
-<p/>On a Unix(-alike) system, using teTeX or TeX Live, the root
-directory will be named something like <i>/usr/share/texmf-local/</i>
-or <i>/usr/local/share/texmf/</i>
-You can ask such a system where it believes a local tree should be:
-<blockquote>
-<pre>
-kpsewhich -var-value TEXMFLOCAL
-</pre>
-</blockquote><p>
-the output being the actual path, for example (on the workstation the
-author is using today):
-<blockquote>
-<pre>
-/usr/local/share/texmf
-</pre>
-</blockquote><p>
-<p/>In a MiKTeX installation, the location will in fact typically be
-something you specified yourself when you installed MiKTeX in the
-first place, but you may find you need to create one. The MiKTeX
-&#8220;Settings&#8221; window (
- <code>Start</code>-&#62;
- <code>Programs</code>-&#62;
- <code>MiKTeX</code>-&#62;
- <code>Settings</code>)
-has a tab &#8220;<code>Roots</code>&#8221;; that tab gives a list of current
-TDS roots (they&#8217;re typically not called
-<code>texmf</code>-anything). If there&#8217;s not one there with
-&#8220;<code>local</code>&#8221; in its name, create an appropriate one (see below),
-and register it using the window&#8217;s
-&#8220;<code>Add</code>&#8221; button.
-<p/>The
-<a href="http://docs.miktex.org/faq/maintenance.html">MiKTeX FAQ</a>
-suggests that you should create
-&#8220;<code>C:\Local TeX Files</code>&#8221;, which is good if you
-manage your own machine, but often not even possible in corporate, or
-similar, environments &#8212; in such situations, the user may have no
-control over the hard disc of the computer, at all.
-<p/>So the real criterion is that your local tree should be somewhere that
-<em>you</em>, rather than the system, control. Restrictive systems often
-provide a &#8220;home directory&#8221; for each user, mounted as a network
-drive; this is a natural home for the user&#8217;s local tree. Other (often
-academic) environments assume the user is going to provide a memory
-stick, and will assign it a defined drive letter &#8212; another good
-candidate location. Note that the semantics of such a tree are
-indistinguishable from those of a
-<a href="FAQ-privinst.html">&#8220;home&#8221; TEXMF tree</a>.
-<p/>There are circumstances when you might not wish to use the &#8216;local&#8217; tree:
-<ul>
-<li> if the package, or whatever, is &#8220;personal&#8221; (for example,
- something commercial that has been licensed to you alone, or
- something you&#8217;re developing yourself), it should go in your
- <a href="FAQ-privinst.html">&#8220;home&#8221; TEXMF tree</a>;
-<li> if you <em>know</em> that the package you are installing is a
- replacement for the copy on the TEXMF tree of your (La)TeX
- distribution, you should replace the existing copy in the
- TEXMF tree.
-</ul>
-The reason one would put things on a local tree is to avoid their
-disappearance if the system is upgraded (or otherwise re-installed).
-<p/>The reason one might place upgrades the distribution&#8217;s main tree is to
-avoid confusion. Suppose you were to place the file on the local
-tree, and then install a new version of the distribution &#8212; you might
-have an effect like:
-<ul>
-<li> distribution comes with package version n;
-<li> you install package version n+1 on the local tree; and
-<li> the updated distribution provides package version n+2.
-</ul>
-In such a situation, you will find yourself using version
-n+1 (from the local tree) <em>after</em> the new
-distribution has been installed.
-<p/>If you install in the local tree, the only way to avoid such problems
-is to carefully purge the local tree when installing a new
-distribution. This is tedious, if you&#8217;re maintaining a large
-installation.
-<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS</a>
-</body>