ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Frank Küster" <frank@kuesterei.ch>
Subject: Re: ConTeXt on Debian: The wiki entry
Date: Tue, 24 Oct 2006 10:24:26 +0200	[thread overview]
Message-ID: <86zmbm5dfp.fsf@alhambra.kuesterei.ch> (raw)
In-Reply-To: <453DBF4C.2090203@elvenkind.com> (Taco Hoekwater's message of "Tue\, 24 Oct 2006 09\:22\:52 +0200")

Taco Hoekwater <taco@elvenkind.com> wrote:

> Frank Küster wrote:
>> 
>> Can you point me to the place where it is documented which calls are
>> needed to be called
>
> I was going to say: on the wiki, but that clearly wouldn't work
> this time.
>
> To actually update ConTeXt, assuming you already have a relatively
> modern context installed, you say
> 	
>    # ctxtools --update
>
> and that fetches the zip file(s) from the pragma site (or a mirror),
> unpacks them, and updates the various perl and ruby scripts that come
> with ConTeXt.

When this is done on a system where ConTeXt first came with a TeXlive or
teTeX installation, will this replace existing files, or will it put the
updated new files in TEMXFLOCAL or TEXMFHOME, respectively?  Ah, I think
you have answered this already below.

> You have to be root for this when you want to update the global install,
> otherwise you have a few extra caveats, see below.
>
> After a succesful update, you have to run
> 	
>   # texexec --make --all [--xetex | --aleph | --pdftex] <formats>
>
> Where <formats> are the desired formats to run. The accepted list
> at the moment is: the eight ConTeXt formats, in both long
> ("cont-en" etc.) and  short from ("en","nl","de","it","fr","cz",
> "ro","uk"), and "mptopdf", and the metapost mems "mpost" and "metafun".

So I guess this is the call that would also be needed if the update
itself goes via a package management, i.e. if one installs a new version
of the Debian ConTeXt package.

> This works fine if you are root, and had a previous context update
> done already. If you have not already and/or are not root, then you
> have two big problems:
>
> * TEXFORMATS as shipped with teTeX/TL is uncomplete: there is that
>    missing format-specific subdirectory. 

So I guess TeXlive (and the existing teTeX packages within
Linux/BSD/... distributions) should do that, so that modern ConTeXt just
works. 


If you are not root, then
>    you have to create a local texmf.cnf to overrule the default
>    texmf.cnf. I have:
>
>    TEXFORMATS    = .;$TEXMF/web2c/{$engine,}
>
>    because context's texexec pushes the $engine setting to the
>    environment, this works fine (Originally this was supposed to
>    be handled by kpathsea, but like I said, that never got off
>    the ground)

It might be possible by setting, in texmf.cnf,

TEXFORMATS.xetex = .;$TEXMF/web2c{xetex,}
TEXFORMATS.pdftex = .;$TEXMF/web2c{pdftex,}

and so on.  I'm not sure, however; this of course depends on which
progname ConTeXt uses (so it might need to be TEXFORMATS.cont-xetex or
whatever). 

>    Not using texexec is not a big deal in itself, as long as you
>    restrict yourself to using pdfetex and know how to edit the
>    fmtutil config file, I guess. That's why you sometimes see that
>    approach promoted on the wiki.

I think, with the TEXFORMATS.$engine setup working, it should be
possible to use both, fmtutil and texexec, and get the same formats -
texexec might still be better in doing other update tasks.

> * TEXFONTMAPS is also wrong: it makes pdftex (and dvipdfmx as well,
>    I guess) find the mapfiles for dvips before their own mapfiles
>    (those are shipped with ConTeXt).

This also sounds like a bug in TeXlive/teTeX.

> * Lastly, ctxtools --update does a kpsewhich on context.tex to find
>    where to install the updated files. That only works if  you have
>    write permission for that directory (i.e. you are root),  or if you
>    have done a private install already.

So this means -update will always try to overwrite an existing
installation, and not automatically search for a writable directory
that's earlier in the TEXMF path?  Even not as a fallback?  This sounds
as if this tool could be improved.

> I think that is all, but I may have missed something, so if you read
> this message and know a thing or two about updating, please double
> check my text. Thanks in advance.

I think it does help a lot, and we can work from there, testing with the
Debian ConTeXt package.

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

  reply	other threads:[~2006-10-24  8:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  8:35 Frank Küster
2006-10-23 10:25 ` Renaud AUBIN
2006-10-23 10:58 ` Taco Hoekwater
2006-10-23 11:39   ` Frank Küster
2006-10-23 18:15     ` Taco Hoekwater
2006-10-23 19:01       ` Frank Küster
2006-10-24  7:22         ` Taco Hoekwater
2006-10-24  8:24           ` Frank Küster [this message]
2006-10-24  8:57             ` Hans Hagen
2006-10-24  8:57             ` Taco Hoekwater
2006-11-01 21:30           ` ctxtools unix puzzles plink
2006-11-01 22:13             ` Hans Hagen
2006-12-25 23:54             ` mkiv files plink
2006-10-25 13:37     ` ConTeXt on Debian: The wiki entry Hans Hagen
2006-10-23 20:47 ` Sanjoy Mahajan
2006-10-23 21:48   ` Hans Hagen
2006-10-24  5:53     ` Frank Küster
2006-10-24  8:18       ` Hans Hagen
2006-10-24  9:01         ` Frank Küster
2006-10-24 11:33           ` Hans Hagen
2006-10-24 13:34             ` Frank Küster
2006-10-24 14:33               ` Hans Hagen
2006-10-25  6:52 ` Gerhard Kugler
2006-10-25  8:55   ` Frank Küster

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=86zmbm5dfp.fsf@alhambra.kuesterei.ch \
    --to=frank@kuesterei.ch \
    --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).