303
edits
Changes
Jump to navigation
Jump to search
The context packages depend on [http://www.tug.org/texlive TeXLive], so if you are using the Debian teTeX packages (e.g. see whether <tt>tetex-base</tt> is installed by doing <code>dpkg -l tetex-base</code>), it's time to change to TeXLive. If you are switching from teTeX, it's important to <b>purge</b>, not just remove the <tt>tetex-*</tt> packages before installing the TeXLive packages. Otherwise the teTeX configuration files, including those in <tt>/etc/texmf/texmf1.d/</tt> and <tt>/etc/texmf/fmt.d/</tt>, will haunt Download the system like a ghost. To purge: apt-get --purge remove tetex-{extra,doc,bin,base}deb The full directions for using TeXLive are at http://wwwpackages.tugdebian.org/texlive/debian.html or[[Debian TeXlive install]], though if you are brave you can just try: apt-get update && apt-get install texlive Once you've installed the basic packages, you'll need a few extras: apt-get install lmodern cm-super texlive-fonts-recommended == Check for shadowing formats and macros == These installation instructions describe a system-wide install. But individual users may have followed the old directions on this page and (sorry!) made a per-user ConTeXt installation; or as root you may have done a system-wide install in, for example, <tt>/usr/local/share/texmf</tt> or other directory that shadows <tt>/usr/share/texmf</tt>. In either case, the system-wide install from the packages won't be seen. If individual users prefer to shadow the system-wide install and to run their downloaded versions, that's fine. But if they want to use the system-wide install (recommended except for those who are testing Hans's latest versions...), then there are two issues. The first issue is old format files. If a user has format files in <tt>~/.texmf-var/web2c/<i>engine<experimental/i><all/tt> where <i>engine</i> is typically <tt>pdfetex</tt>, then these will shadow the ones installed by the context package. So the user should delete the ConTeXt-related ones, such as <tt>cont-*.fmt</tt>, <tt>mptopdf.fmt</tt>, and <tt>metafun.mem</tt>. To find them, the user can do: kpsewhich cont-en.fmt or kpsewhich -engine pdfetex cont-en.fmt (and similarly for the other formats). Run it from a 'typical' directory (e.g. <tt>~</tt>), rather than from <tt>~/.texmf-var/web2c/pdfetex/</tt> (adjust for your engine), otherwise it will find the newly created formats before any others even if they are not shadowing anything else. The second issue is the ConTeXt macros. If a user has installed them a directory that shadows <tt>/usr/share/texmf</tt>, then they will be found rather than the system-wide ones. So move the shadowing context installations out of the way. The user can check with kpsewhich cont-new.tex and make sure that it's not finding any (until you do the system-wide install, of course). That should do it! The output of <code>ctxtools --contextversion</code> is hopefully like this: <code> CtxTools | context version: 2008.05.21 15:21 (/usr/share/texmf/tex/context/base/context.tex) CtxTools | context version: 2008.05.21 15:21 (/usr/share/texmf/tex/context/base/cont-new.tex)</code> The long path to <tt>context.tex</tt> and <tt>cont-new.tex</tt> show where the system thinks the context macros are installed. Make sure your installation is finding those versions!download
no edit summary
* in december 2010 a new experimental .deb package was built you can try it out: http://packages.debian.org/experimental/context
== switch from tetex to texlive = install latest experimental context .deb package ===
2. run as root
dpkg -i context_2010.07.30-1_all.deb
You have now a system wide context-installation!
== See also ==
