summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html126
1 files changed, 0 insertions, 126 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html
deleted file mode 100644
index bc3e74ca2e9..00000000000
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html
+++ /dev/null
@@ -1,126 +0,0 @@
-<head>
-<title>UK TeX FAQ -- question label privinst</title>
-</head><body>
-<h3>&#8220;Private&#8221; installations of files</h3>
-<p/>It sometimes happens that you need a new version of some macro package
-or font, but that the machine you use is maintained by someone who&#8217;s
-unwilling to update and won&#8217;t give you privileges to do the job
-yourself. A <a href="FAQ-tempinst.html">&#8220;temporary&#8221; installation</a> is
-sometimes the correct approach, but if there&#8217;s the slightest chance
-that the installation will be needed on more than one project,
-temporary installations aren&#8217;t right.
-<p/>In circumstances where you have plenty of quota on backed-up media, or
-adequate local scratch space, the correct approach is to create a
-private installation of (La)TeX which includes the new stuff you
-need; this is the ideal, but is not generally possible.
-<p/>So, since you can&#8217;t install into the public <code>texmf</code> tree, you
-have to install into a <i>texmf</i> tree of your own; fortunately, the
-TDS standard allows for this, and modern distributions allow
-you to do it. The most modern distributions refer to the tree as
-<code>$TEXMFHOME</code>, but it used to be called <code>$HOMETEXMF</code>;
-so to check that your TeX system does indeed support the mechanism
-you should start with
-<pre>
-kpsewhich -var-value TEXMFHOME
-</pre>
-(for example). This will almost invariably return a pointer to a
-subdirectory <i>texmf</i> of your home directory; the commonest
-exception is Macintoshes, using MacTeX, where the diretory is
-conventionally <i>Library/texmf</i> in your home directory.
-<p/>If you can confirm that the technique does indeed work, install your
-new package (or whatever) in the <a href="FAQ-install-where.html">correct place</a>
-in a tree based on <i>$HOME/texmf</i>, and generate an index of that
-tree
-<blockquote>
-<pre>
-texhash $HOME/texmf
-</pre>
-</blockquote><p>
-(the argument specifies which tree you are indexing: it&#8217;s necessary
-since you don&#8217;t, by hypothesis, have access to the main tree, and
-<i>texhash</i> without the argument would try to write the main
-tree.
-<p/>There are two wrinkles to this simple formula: first, the installation
-you&#8217;re using may <em>not</em> define a home TEXMF directory, and second,
-there may be some obstruction to using <i>$HOME/texmf</i> as the
-default name. In either case, a good solution is to have your own
-<i>texmf.cnf</i> &#8212; an idea that sounds more frightening that it
-actually is. The installation&#8217;s existing file may be located with the
-command:
-<blockquote>
-<pre>
-kpsewhich texmf.cnf
-</pre>
-</blockquote><p>
-Take a copy of the file and put it into a directory of your own; this
-could be any directory, but an obvious choice is the <i>web2c</i>
-directory of the tree you want to create, i.e.,
-<i>$HOME/texmf/web2c</i> or the like. Make an environment variable to
-point to this directory:
-<blockquote>
-<pre>
-TEXMFCNF=$HOME/texmf/web2c
-export TEXMFCNF
-</pre>
-</blockquote><p>
-(for a Bourne shell style system), or
-<blockquote>
-<pre>
-setenv TEXMFCNF $HOME/texmf/web2c
-</pre>
-</blockquote><p>
-(for a C-shell style system). Now edit the copy of <i>texmf.cnf</i>
-<p/>There will be a line in the existing file that defines the tree where
-everything searches; the simplest form of the line is:
-<blockquote>
-<pre>
-TEXMF = !!$TEXMFMAIN
-</pre>
-</blockquote><p>
-but, there are likely to be several alternative settings behind
-comment markers (&#8220;<code>%</code>&#8221;), and the person who
-installed your system may have left them there. Whatever, you need to
-modify the line that&#8217;s in effect: change the above to three lines:
-<blockquote>
-<pre>
-HOMETEXMF = $HOME/texmf
-TEXMF = {$HOMETEXMF,!!$TEXMFMAIN}
-% TEXMF = !!$TEXMFMAIN
-</pre>
-</blockquote><p>
-the important point being that <code>$HOMETEXMF</code> must come before
-whatever was there before, inside the braces. For example, if the
-original was
-<blockquote>
-<pre>
-TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
-</pre>
-</blockquote><p>
-it should be converted to:
-<blockquote>
-
-<pre>
-HOMETEXMF = $HOME/texmf
-TEXMF = {$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
-% TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
-</pre>
-</blockquote><p>
-(retaining the original, as a comment, is merely an aide-memoir in
-case you need to make another change, later). The <code>!!</code> signs
-tell the file-searching library that it should insist on a
-<i>texhash</i>-ed directory tree; if you can count on yourself
-remembering to run <i>texhash</i> on your new tree every time you
-change it, then it&#8217;s worth adding the marks to your tree:
-<blockquote>
-
-<pre>
-TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
-</pre>
-</blockquote><p>
-as this will make (La)TeX find its files marginally faster.
-<p/>Having made all these changes, (La)TeX should &#8220;just use&#8221; files in
-your new tree, in preference to anything in the main tree &#8212; you can
-use it for updates to packages in the main tree, as well as for
-installing new versions of things.
-<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst</a>
-</body>