ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: bb <skip.collins@gmail.com>
Subject: Re: INstalling a new version of context
Date: Sun, 8 May 2005 23:01:59 -0400	[thread overview]
Message-ID: <f03b6a44050508200158c15ef2@mail.gmail.com> (raw)
In-Reply-To: <20050508100002.AAEAA127B3@ronja.ntg.nl>

> The upgrading of Context or even of pdftex is sufficiently
> failure prone that I have given up trying.

I tend to agree. I follow the meager instructions I have found, as
well as some direct help from hh himself and am still not able to get
it working right. I think the problem is with hacked engine support. I
try disabling the use of engine but I still get the same problem. At
this point I am tracking down a weird error in texexec.pl in which
kpsewhich returns a null result and TEXFORMATS gets set to '0'. This
wreaks havoc and breaks everything. I suspect texlive texmf.cnf
settings trigger a bug in texexec.

Perhaps everything would work just fine with the limited linux tex
distribution from pragma. But I, like many others, prefer to use
texlive because it is fairly comprehensive and I can use my normal
latex and friends. I think it would be a very useful exercise for hh
to install a complete texlive on a stock fedora box. Then write down
_every_ step necessary to get beta cont-tmf.zip installed and working.
I would think that targeting texlive as the standard platform for
distributing context on linux/unix would make the most sense. It
should _not_ be necessary to make anything but a trivial change to
texmf.cnf.

sc

       reply	other threads:[~2005-05-09  3:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050508100002.AAEAA127B3@ronja.ntg.nl>
2005-05-09  3:01 ` bb [this message]
2005-05-09  9:18   ` Taco Hoekwater
2005-05-09 15:45     ` bb
2005-05-09 17:01       ` Taco Hoekwater
2005-05-09 19:12         ` bb
2005-05-10 12:45           ` texexec.pl patch bb
2005-05-09 20:21       ` INstalling a new version of context Hans Hagen
2005-05-07 18:01 olibou
2005-05-07 20:29 ` John R. Culleton
2005-05-08  8:18   ` olibou
2005-05-08 20:40   ` Hans Hagen
2005-05-08 20:44 ` Hans Hagen
2005-05-09 10:24   ` John R. Culleton

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=f03b6a44050508200158c15ef2@mail.gmail.com \
    --to=skip.collins@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=skip@interbit.com \
    /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).