Changes

Jump to navigation Jump to search
4,597 bytes removed ,  00:46, 14 February 2022
m
== Use TeXLive packages == The context packages depend {{note|Releases of Debian (or any other distribution for that matter) usually contain way too old TeX distributions for ConTeXt MKIV (but should work fine for MKII). If you want to live on [http://www.tug.org/texlive TeXLive]bleeding edge, so if you are consider using the packages from Debian teTeX packages (e.g. see whether tetex-base is installed by doing "dpkg -l tetex-base")/unstable, it's time to make the change to TeXLive. You'll have to do it eventually since teTeX 3.0 will be its last upstream release. So if not now[[ConTeXt Standalone]], when? The directions for using TeXLive are or at http://www.tug.org/texlive/debian.html Make sure you least install the texlive-metapost package if you do not have it already.   == Install a latest version of [[TeX Live]] with [[Latin ModernTLContrib]] font update == Do<code> # apt-get install lmodern cm-super</code>manually.}}
== Install the ConTeXt packages ==
Norbert Preining has produced reliable, complete The status of ConTeXt packages for in Debian/unstable is currently up to date with TeX Live 2021, and they use very recent versions of ConTeXt (as of this writingincludes all the necessary bits and pieces, which is 2007.01.05, the latest package has plus the 2007.01.02 version of ConTeXt). Here's how to use them. Add these two lines to your /etc/apt/sources.list :  deb <nowiki>http://www.tugmodules shipped in TeX Live.org/texlive/Debian/</nowiki> context/ deb-src <nowiki>http://www.tug.org/texlive/Debian/</nowiki> context/
If you are running Debian sid or later, then the <code>context</code> and <code>context-modules</code> packages should already be visible.
Then do
apt-get aptitude update apt-get aptitude install context context-nonfree context-doc-nonfree and apt will download and install the latest ConTeXt packages. == Steps to finish a first context upgrade == The Debian tetex-3.0 package (and probably the vanilla tetex-3.0) in combination with <tt>texexec</tt> puts user-generated format files in <tt>~/.texmf-var/web2c/<i>engine</i></tt> where <i>engine</i> is typically <tt>pdfetex</tt>. (If you don't have such a directory, and you are using the default tetex configuration, tell the mailing list so that this installation information can be corrected!) The default <tt>tetex</tt> setup doesn't know about such locations (it doesn't know what it should), and it instead knows about other locations (it knows what it shouldn't). Here is how to fix both problems. === Older context formats === There may be older context formats lying around, and the path searching code may find these older ones instead of the new ones lovingy made by <tt>texexec</tt>. ==== Deleting the older context formats ==== So you need delete the older ones. But where are they? When I ran <tt>texexec</tt>, it made <tt>cont-en.fmt</tt>, <tt>cont-nl.fmt</tt>, and <tt>mptopdf.fmt</tt> in <tt>~/.texmf-var/web2c/pdfetex/</tt> and they were shadowed by the older versions: <tt>~/.texmf-var/web2c/cont-en.fmt</tt>, etc. So I deleted the older ones.  If you cannot find them, use <tt>kpsewhich cont-en.fmt</tt> (and similarly for the other formats). Run the <tt>kpsewhich</tt> from a 'typical' directory (e.g. your home directory), rather than from <tt>~/.texmf-var/web2c/pdfetex/</tt> (adjust for your engine), otherwise it will find the newly created formats before any others.  ==== Stopping fmtutil from making context-related formats ==== But how did the older ones get there? <tt>fmtutil</tt> And will it happen again? Yes, though perhaps rarely (the most frustrating kind of bug). At the next upgrade of <tt>tetex</tt>, which happens frequenty on Debian, the installation scripts will rerun <tt>fmtutil</tt> as root. That probably won't cause you trouble because the formats generated will go in a system-wide format directory (e.g. in <tt>/var/lib/texmf/web2c/</tt>), and your new ones will override them once you finish these steps.  However, if you, as an ordinary user, run <tt>texconfig</tt>, say to change your own default paper size from <tt>letter</tt> to <tt>a4</tt>, then <tt>tetex</tt> will regenerate all formats for you and put them in your format location <tt>~/.texmf-var/web2c/</tt> (without using the engine subdirectory). And you're in the soup again. So stop <tt>fmtutil</tt> from making any context-related formats, and let <tt>texexec</tt> handle it. On standard <tt>tetex</tt> setups, you'd edit <tt>fmtutil.cnf</tt> (probaby in <tt>/var/lib/texmf/web2c/</tt>), but on Debian systems, that file is autogenerated from configlets (tiny pieces of a config file) living in <tt>/etc/texmf/fmt.d/</tt>.  As <tt>root</tt>:modules
emacs -nw /etc/texmf/fmt* The final version in debian bullseye (aka debian stable 11.2) is 2020.03.d/01tetex10.cnf20200331-1* In ''unstable'' is a version that is from the TeX Live 2021
(or choose your favorite editor)=== Install latest unstable context . Comment out (with a <tt>#!</tt>) the lines for <tt>mptopdf</tt>, <tt>metafun</tt>, <tt>cont-en</tt>, and any other <tt>cont-*</tt> formats not already commented out. Now generate a new system-wide configuration file:deb package ===
update-fmtutil<tt>unstable</tt> means ''(mature) development'', the version number may changes. The software is ''stable''
=== Finding 1. Download the new formats ===two .deb-s http://packages.debian.org/unstable/all/context/downloadhttp://packages.debian.org/unstable/all/context-modules/download
The path searching code will not find 2. run as root (the newer formats because the code doesn't search subdirectories of <tt>web2c/</tt>. version number might have increased a bit) The simple fix, telling it to search all subdirectories, does not work: Context may use several different engines, e.gdpkg --install context_2021. <tt>pdfetex</tt> or <tt>xetex</tt>, each with a set of formats, and you want <tt>texexec</tt> to find the correct set03. If it searches all subdirectories, it will use the first set that it happens to run across, which may not match the engine that you use05. Instead the searches should look in the subdirectory chosen according to the <i>engine</i>20220211-1_all. deb mtxrun --generate
To specify this kind of search, you'd normally edit <tt>texmf.cnf</tt> directly, but Debian uses configlets for it3. run as user So edit (still as root) the <tt>TEXFORMATS</tt> line in <tt>/etc/texmf/texmf.d/45TeXinputs.cnf</tt> to include this magic:mtxrun --generate
TEXFORMATS = Step 2.;$TEXMF/web2c/{$engineis currently still necessary,} It says to look first in the <i>engine</i> subdirectory, then in the <tt>web2c</tt> directory itself. Now but soon an update of tex-common will run mtxrun --generate a new <tt>texmf.cnf</tt> configuration file automatically when packages have changed (still as rootlike mktexlsr):, and there will be no need to run this anymore.
update-texmfStep 3. needs to be done only when you have files in TEXMFHOME or you change things there.
That step generates You have now a new <tt>/etc/texmf/texmf.cnf</tt>, which Debian symlinks from its standard tetex location <tt>/usr/share/texmf/web2c/texmf.cnf</tt>. With luck, you are done. In the next section you will check whether everything is working by running <tt>texexec system wide context--version</tt> (as yourself, not as rootinstallation!).
== Finished! See also ==
That should do it! The output of <code>texexec --version</code> (run as you, not as root) is hopefully like this:<code> TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE 1992-2004 tex : pdfeTeXk, 3.141592-1.30.4-2.2 (Web2C 7.5.5) context : ver: 2005.10.27 cont-en : ver: 2005.10.27 fmt: 2005.11.1 mes: english</code>{{Installation navbox}}
[[Category:Installation]]
See also the [[Debian TeXlive install]] page.
174

edits

Navigation menu