ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: ConTeXt on Debian: The wiki entry
Date: Tue, 24 Oct 2006 10:57:32 +0200	[thread overview]
Message-ID: <453DD57C.3040302@wxs.nl> (raw)
In-Reply-To: <86zmbm5dfp.fsf@alhambra.kuesterei.ch>

Frank � wrote:
>   
>> 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.
>   
i think that it depends on what users want to use (pdftex, aleph, xetex, 
luatex, a combination)

ok, one can play safe and just generate them all for the english user 
interface
>
> 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
>   
just curious: how many tex users or people updating tex don't have root 
permissions

> 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). 
>   
the progname is always 'context'

there is no functional difference between context's, only user interface 
languages may differ, so for pdftex, xetex etc the same context is used; 
backend support is loaded runtime; so, there is not, as with latex, a 
pdfcontext or so: backend support has always been isolated in driver 
files; the TEXFORMATS variable should have an /{engine,} appended which 
makes the engine specific formats end up the and be searched there 
(because formats are always generated in a current path, texexec will 
chdir to an engine path when making a format)

so, pdftex, xetex, aleph, ... all use cont-en.fmt for the english user 
interface (used to be cont-en.efmt, cont-en.ofmt, etc);  using 
different  names for the formats does not make sense since the 
functionality is mostly the same
>
> 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.
>   
the problem with this is that there is only one dimensions: progname, so 
TEXFORMATS.context is ok, and TEXFORMATS.xetex is undefined (actually 
$engine is unset in many cases)
>   
>> * 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.
>   
if i'm right Karl added it after we discussed this feature but i didn't 
check it
>   
>> * 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.
>   
 def locatedlocaltree
            tree = Kpse.used_path('TEXMFLOCAL')
            unless tree && FileTest.directory?(tree) then
                tree = Kpse.used_path('TEXMF')
            end
            return tree
        end

so, it prefers texmflocal; so far no one asked for different methods but 
it can always be improved (and will be on request)
>   
>> 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.
>   
ok, thanks. there are debian users on this list so testing should be no problem 

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
-----------------------------------------------------------------

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-10-24  8:57 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
2006-10-24  8:57             ` Hans Hagen [this message]
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=453DD57C.3040302@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).