From: Norbert Preining <preining@logic.at>
Cc: debian-tex-maint@lists.debian.org
Subject: Re: ConTeXt installtion and Debian
Date: Tue, 24 Oct 2006 18:51:24 +0200 [thread overview]
Message-ID: <20061024165124.GA6207@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <20061024110408.GF1371@gamma.logic.tuwien.ac.at>
Hi all!
On Die, 24 Okt 2006, Norbert Preining wrote:
> > # 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".
Ok, I have rewritten the Debian context package so that it does the
following:
On installation/update time a script context-build-formats is called
which reads the file
/etc/texmf/context/formats.cnf
where all the formats to be build are defined. Currently my file looks
like this:
#
# This file defines which ConTeXt formats are build
#
{pdftex,aleph} {de,en,it,mptopdf}
Yes, it expands the curly braces.
On removal currently I don't do anything, because I don't know how to
know which files should be removed. But this shouldn't be to hard,
remove /usr/share/texmf/web2c/$engine/$format.*
Anyway, it is not very intellignet the script, no error checking,
nothing, but it runs.
What do you say:
- you ConTeXt people: concerning the format file, the way of updating?
- you Debian people: concerning the new way to define it?
The context-build-formats should be something like fmtutil(-sys) for
context. I didn't come around to implement the difference between the
-sys and the normal variant, but it should be easy, as in fmtutil-sys.
Any suggestions?
BTW, here is the code for the script, it is short:
#!/bin/bash
# context-build-formats
export TEXMFSYSCONFIG=/usr/share/texmf
parse_line()
{
engine=$1
format=$2
eval set $engine
allengines="$@"
eval set $format
allformats="$@"
for e in $allengines ; do
for f in $allformats ; do
texexec --make --$e $f
done
done
}
OIFS=$IFS
IFS='
'
set $(echo x; sed '/^#/d; /^[ ]*$/d' "/etc/texmf/context/formats.cnf")
; shift
IFS=$OIFS
for line
do
parse_line $line;
done
# eof
You see where I robbed the code ... fmtutil.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Università di Siena
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
SKETTY (n.)
Apparently self-propelled little dance a beer glass performs in its
own puddle.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-tex-maint-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
next prev parent reply other threads:[~2006-10-24 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 11:04 Norbert Preining
2006-10-24 11:13 ` Norbert Preining
2006-10-24 11:42 ` Frank Küster
2006-10-24 12:08 ` Hans Hagen
2006-10-25 9:50 ` Hans Hagen
2006-10-24 16:51 ` Norbert Preining [this message]
2006-10-24 20:37 ` Ralf Stubner
2006-10-25 7:48 ` Hans Hagen
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=20061024165124.GA6207@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=debian-tex-maint@lists.debian.org \
/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).