From: Hans Hagen <pragma@wxs.nl>
Subject: Re: version dates confuse me after upgrade
Date: Thu, 06 Apr 2006 22:40:31 +0200 [thread overview]
Message-ID: <44357CBF.60808@wxs.nl> (raw)
In-Reply-To: <E1FRZGY-0003du-00@skye.ra.phy.cam.ac.uk>
Sanjoy Mahajan wrote:
> that method rather than the raw tetex method. For one, xpdf has
> recurring buffer overruns being discovered, and tetex (at least on
>
afaik this does not affect pdftex, since it uses only a small part of
the xpdf library
> * deleted the ~/.texmf-var/web2c/{cont-en,mptopdf}.fmt (I didn't have
> any metafun formats or I would delete them too).
>
hm, i could let texexec do that
> * did "(cd ; kpsewhich --format=fmt cont-en )" to find any other
> instances of cont-en.fmt, and then remove it:
> rm /var/lib/texmf/web2c/cont-en.fmt
> Same for mptopdf and (if any) metafun.
>
if you use newtexexe it will report more details about what it finds (it
is also more clever in making formats)
> * Edited the TEXFORMATS line in /etc/texmf/texmf.d/45TeXinputs.cnf to
> have the /{$engine,} magic:
> TEXFORMATS = .;$TEXMF/web2c/{$engine,}
>
texexec / newtexexec dixes that runtime; afaik the tex live texmf.cnf
file has engine support (so i expected tetex to provide that as well,
even if it's not used)
> * As root, ran update-texmf to regenerate /etc/texmf/texmf.cnf
>
ah ... i hate that kind of duplications ... a source of hard to trace
problems; the teds (tex directory structure) is around for a while and
rather stable so i wonder why such config files have to en dup in etc;
just don't call it a config file; also, the kpse texmf.cnf model
provides for multiple cnf files
i remember from long ago that there's also some path trickery involved
(btw, i'm not sure where the binaries live)
(btw, beware not to install tex live and tetex alongside )
> * Checked whether the new formats are found:
> $ (cd ; kpsewhich -format=fmt --engine=pdfetex cont-en mptopdf metafun)
> /home/sanjoy/.texmf-var/web2c/pdfetex/cont-en.fmt
> /home/sanjoy/.texmf-var/web2c/pdfetex/mptopdf.fmt
> (No metafun yet, but that's okay.)
>
> * Looks okay, so run 'texexec --version' to see whether it really is okay.
>
newtexexec --check
> Should I add these steps to the Wiki in the Debian installation page?
>
sure
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-04-06 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 5:21 Sanjoy Mahajan
2006-04-06 8:14 ` Hans Hagen
2006-04-06 15:38 ` Sanjoy Mahajan
2006-04-06 15:58 ` Hans Hagen
2006-04-06 16:06 ` Taco Hoekwater
2006-04-06 21:17 ` Gerben Wierda
2006-04-06 22:10 ` Taco Hoekwater
2006-04-06 22:31 ` Hans Hagen
2006-04-06 18:31 ` Sanjoy Mahajan
2006-04-06 19:36 ` Taco Hoekwater
2006-04-06 21:07 ` Thomas A. Schmitz
2006-04-07 20:31 ` Sanjoy Mahajan
2006-04-08 8:56 ` Hans Hagen
2006-04-08 12:01 ` Sanjoy Mahajan
2006-04-08 12:40 ` Hans Hagen
2006-04-06 20:40 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44357CBF.60808@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).