From: Ralf Stubner <ralf.stubner@web.de>
Cc: "Frank Küster" <frank@debian.org>,
ntg-context@ntg.nl, taco@elvenkind.com,
debian-tex-maint@lists.debian.org
Subject: Re: ConTeXt installtion and Debian
Date: Tue, 24 Oct 2006 22:37:39 +0200 [thread overview]
Message-ID: <20061024203739.GJ3391@thinkpad> (raw)
In-Reply-To: <20061024165124.GA6207@gamma.logic.tuwien.ac.at>
On Tue, Oct 24, 2006 at 18:51 +0200, Norbert Preining wrote:
>
> 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.
Minor point: /etc/texmf is a TEXMF tree that IMHO should follow TDS,
hence
/etc/texmf/tex/context/formats.cnf
might be more appropriate.
> 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.*
Really /usr/share? To which tree are format files written?
> BTW, here is the code for the script, it is short:
> #!/bin/bash
> # context-build-formats
> export TEXMFSYSCONFIG=/usr/share/texmf
Why that? (Probably related to the question to which tree format files
are written.)
cheerio
ralf
next prev parent reply other threads:[~2006-10-24 20:37 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
2006-10-24 20:37 ` Ralf Stubner [this message]
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=20061024203739.GJ3391@thinkpad \
--to=ralf.stubner@web.de \
--cc=debian-tex-maint@lists.debian.org \
--cc=frank@debian.org \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.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).