Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision
Révision précédente
fichiers:tds:la_tds3 [2018/06/03 13:11] samcarterfichiers:tds:la_tds3 [2021/01/17 20:49] (Version actuelle) – Suppression d'un signe de ponctuation inutile dbitouze
Ligne 1: Ligne 1:
---- +====== Which tree to use? ====== 
-title: Which tree to use +
-category: installing +
-permalink: /FAQ-what-TDS +
-redirect_from: /FAQ-what-tds +
-date: 2014-06-10 +
----+
  
 In almost all cases, new material that you install should go into the In almost all cases, new material that you install should go into the
 "local" tree of your (La)TeX installation.  (A discussion of "local" tree of your (La)TeX installation.  (A discussion of
-reasons _not_ to use the local tree appears below.)+reasons //not// to use the local tree appears below.)
  
-On a Unix(-alike) system, using TeX Live or teTeX, the root +On a Unix(-alike) system, using TeX Live or teTeX, the root 
-directory will be named something like `/usr/share/texmf-local/` +directory will be named something like ''/usr/share/texmf-local/'' 
-or `/usr/local/share/texmf/`+or ''/usr/local/share/texmf/''
 You can ask such a system where it believes a local tree should be: You can ask such a system where it believes a local tree should be:
-```latex+ 
 +<code bash>
 kpsewhich -var-value TEXMFLOCAL kpsewhich -var-value TEXMFLOCAL
-```+</code>
 the output being the actual path, for example (on the workstation this the output being the actual path, for example (on the workstation this
 author is using today): author is using today):
-```latex+ 
 +<code bash>
 /usr/local/share/texmf /usr/local/share/texmf
-```+</code>
  
 In a MiKTeX installation, the location will in fact typically be In a MiKTeX installation, the location will in fact typically be
 something you specified yourself when you installed MiKTeX in the something you specified yourself when you installed MiKTeX in the
 first place, but you may find you need to create one.  The MiKTeX first place, but you may find you need to create one.  The MiKTeX
-"Settings" window ( +"Settings" window ( ''Start'' $\rightarrow$ ''Programs'' $\rightarrow$ 
-  `Start`&rarr; +''MiKTeX'' $\rightarrow$ ''Settings'') has a tab ''Roots''; 
-  `Programs`&rarr; +that tab gives a list of current TDS roots (they're typically not 
-  `MiKTeX`&rarr; +called ''texmf''-anything).  If there's not one there with 
-  `Settings`) +''local'' in its name, create an appropriate one (see below), 
-has a tab `Roots`; that tab gives a list of current +and register it using the window'''Add'' button.
-TDS roots (they're typically not called +
-`texmf`-anything).  If there's not one there with +
-`localin its name, create an appropriate one (see below), +
-and register it using the window's +
-`Addbutton.+
  
-The  +The [[http://docs.miktex.org/faq/maintenance.html|MiKTeX FAQ]] 
-[MiKTeX FAQ](http://docs.miktex.org/faq/maintenance.html) +suggests that you should create ''C:\\Local TeX Files'', which is good if you
-suggests that you should create  +
-`C: Local TeX Files`, which is good if you+
 manage your own machine, but often not even possible in corporate, or manage your own machine, but often not even possible in corporate, or
-similar, environments&nbsp;&mdash; in such situations, the user may have no+similar, environments --- in such situations, the user may have no
 control over the hard disc of the computer, at all. control over the hard disc of the computer, at all.
 +
 +FIXME Ce n'est plus vrai, MiKTeX propose maintenant de s'installer sous ''C:\Users\...\AppData\Local\Programs''.
  
 So the real criterion is that your local tree should be somewhere that So the real criterion is that your local tree should be somewhere that
-_you_, rather than the system, control.  Restrictive systems often+//you//, rather than the system, control.  Restrictive systems often
 provide a "home directory" for each user, mounted as a network provide a "home directory" for each user, mounted as a network
 drive; this is a natural home for the user's local tree.  Other (often drive; this is a natural home for the user's local tree.  Other (often
 academic) environments assume the user is going to provide a memory academic) environments assume the user is going to provide a memory
-stick, and will assign it a defined drive letter&nbsp;&mdash; another good+stick, and will assign it a defined drive letter --- another good
 candidate location.  Note that the semantics of such a tree are candidate location.  Note that the semantics of such a tree are
-indistinguishable from those of a  +indistinguishable from those of a [[FAQ-privinst|"home" TEXMF tree]].
-["home" TEXMF tree](FAQ-privinst).+
  
 You might not wish to use the 'local' tree: You might not wish to use the 'local' tree:
-   +  if the package, or whatever, is "personal" (for example, something commercial that has been licensed to you alone, or something you're developing yourself), it should go in your [[FAQ-privinst|"home" TEXMF tree]]
- +  if you //know// that the package you are installing is a replacement for the copy on the TEXMF tree of your (La)TeX distribution; in this case it is reasonable to replace the existing copy in the TEXMF tree.
--  if the package, or whatever, is "personal" (for example, +
-    something commercial that has been licensed to you alone, or +
-    something you're developing yourself), it should go in your +
-    ["home" TEXMF tree](FAQ-privinst)+
- if you _know_ that the package you are installing is a +
-    replacement for the copy on the TEXMF tree of your (La)TeX +
-    distribution; in this case it is reasonable to replace the existing +
-    copy in the TEXMF tree.+
  
 If the system is upgraded (or otherwise re-installed), a copy made in If the system is upgraded (or otherwise re-installed), a copy made in
 the TEXMF tree will probably be overwritten or deleted.  This the TEXMF tree will probably be overwritten or deleted.  This
 may be what you want, but otherwise it's a powerful incentive to use a may be what you want, but otherwise it's a powerful incentive to use a
-tree that is _not_ "part of the installed system".+tree that is //not// "part of the installed system".
  
 The reason one might place upgrades the distribution's main tree is to The reason one might place upgrades the distribution's main tree is to
 avoid confusion.  Suppose you were to place the file on the local avoid confusion.  Suppose you were to place the file on the local
-tree, and then install a new version of the distribution&nbsp;&mdash; you might+tree, and then install a new version of the distribution --- you might
 have an effect like: have an effect like:
-   +  distribution comes with package version n; 
- +  you install package version n+1 on the local tree; and 
--  distribution comes with package version n; +  the updated distribution provides package version n+2.
- you install package version n+1 on the local tree; and +
- the updated distribution provides package version n+2.+
  
 In such a situation, you could find yourself using version In such a situation, you could find yourself using version
-n+1 (from the local tree) _after_ the new+n+1 (from the local tree) //after// the new
 distribution has been installed. distribution has been installed.
  
Ligne 93: Ligne 74:
 installation. installation.
  
 +
 +-----
 +//Source://
 +  * [[faquk>FAQ-what-TDS|Which tree to use]]
 +
 +{{htmlmetatags>metatag-keywords=(LaTeX,installer LaTeX,TeX Directory structure,installation,répertoire pour LaTeX)
 +metatag-og:title=(Which tree to use?)
 +metatag-og:site_name=(FAQ LaTeX francophone)
 +}}
  
5_fichiers/tds/la_tds3.1528031484.txt.gz · Dernière modification : 2018/06/03 13:11 de samcarter
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0