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 15:34:40 +0200	[thread overview]
Message-ID: <86hcxt25xr.fsf@alhambra.kuesterei.ch> (raw)
In-Reply-To: <453DFA02.2030106@wxs.nl> (Hans Hagen's message of "Tue\, 24 Oct 2006 13\:33\:22 +0200")

Hans Hagen <pragma@wxs.nl> wrote:

[ horror story snipped ]
> anyhow, by now, no alias file should be present in any tex root any 
> more; it was a bad idea anyway

I always thought that the purpose of the aliases file was that a
non-existent (no, nay, never, nowhere ever) filename was aliased to an
existent one, like in the documentation part:

% documentation
TETEXDOC.pdf teTeX.pdf
etex-man.pdf etex.pdf
pdftex-a.pdf pdftex.pdf
testeuro.dvi eurosym.dvi

If the rest of the aliases covers files that might exist as real files
on some systems - I agree, what a bad idea.

> pool files normally are in web2c paths; future versions of pdftex and 
> mpost have the pool file embedded so this problem will (hopefully) disappear

Ah, I didn't know that.  pdftex 1.40 doesn't have this already, has it?

> hm, interesting; lean and mean texmf.cnf files can speed up things a lot
>
> when playing with luatex (where i intend to replace kpse completely with 
> a lua based variant) it is possible to have format specific file 
> databases; this runs much faster; this whole ls-r stuff is pretty outdated

Oh, yes, it is.  Current kpse also has the "side effect" that on most
systems, users are able to fill up the /var/ partition by generating
pixel fonts...  

Karl (or was it Olaf?) once said there are plans for a complete
replacement of libkpathsea, named kpse - would that be obsolete with
luatex?  Could there be a C wrapper about lua's kpse?

> sure, but (i'm not sure if this is still true) running tex live 
> alongside a tetex was always kind of problematic due to path settings 
> and this autoparent mess then deriving locations of texmf.cnf from it

This is probably still a problem in standard-setup systems.  

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 13:34 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
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 [this message]
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=86hcxt25xr.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).