Changes

== Steps to finish a first context upgrade Check for shadowing formats and macros ==

If you These installation instructions describe a system-wide install. But individual users may have format files in <tt>~/followed the old directions on this page and (sorry!) made a per-user ConTeXt installation.texmf-var/web2c/<i>engine</i></tt> where <i>engine</i> is typically <tt>pdfetex</tt>, then these Those will shadow the ones installed by the context packagesystem-wide install. So you need delete themIf that's what they want to do, no problem.

To find them, But if they want to use <tt>kpsewhich contthe system-en.fmt</tt> wide install (and similarly recommended except for the other formats). Run the <tt>kpsewhich</tt> from a those who are testing Hans'typical' directory (es latest versions.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 othersthen there are two issues.

The first issue is old format files. If you have context installed a user has format files in a directory that precedes <tt>~/.texmf-var/web2c/<i>engine</usri></sharett> where <i>engine</texmfi> is typically <tt>pdfetex</tt>, then they 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 you will get similarly for the other formats). Run it from a clash 'typical' directory (e.g. <tt>~</tt>), rather than from <tt>~/.texmf-var/web2c/pdfetex/</tt> (adjust for your engine), otherwise it will find the format files will be newly created formats before any others even if they are not shadowing anything else. The second issue is the ones ConTeXt macros. If a user has installed by the packagethem a directory that shadows <tt>/usr/share/texmf</tt>, but later versions then they will be read in)found rather than the system-wide ones. So you need to 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).