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 07:53:55 +0200	[thread overview]
Message-ID: <86hcxufedo.fsf@alhambra.kuesterei.ch> (raw)
In-Reply-To: <453D38AD.1010608@wxs.nl> (Hans Hagen's message of "Mon\, 23 Oct 2006 23\:48\:29 +0200")

Hans Hagen <pragma@wxs.nl> wrote:

> Sanjoy Mahajan wrote:
>> A system-wide installation, if done cleanly, would be much easier
>> (as plink pointed out).  If you (or 'texexec --make' to generate the
>> formats) ask kpathsea where to put the format files, it'll give you
>> a directory in TEXMFHOME, so a per user install.  But how do you ask
>> kpathsea the correct question so that it'll tell you where they
>> should go for a system-wide install?
>>   
> you can't and i remember asking for such a feature but ... ;

Can you point me to this discussion?  I think it doesn't need more as
what fmtutil-sys, updmap-sys and texconfig-sys do before calling
fmtutil, updmap or texconfig, respectively:

v=`kpsewhich -var-value TEXMFSYSVAR`
c=`kpsewhich -var-value TEXMFSYSCONFIG`

TEXMFVAR="$v"
TEXMFCONFIG="$c"
export TEXMFVAR TEXMFCONFIG

exec updmap ${1+"$@"}

However, it would be probably more elegant and context-like to not have
texexec and texexec-sys, but rather a commandline switch - in this case
the handling would have to be done in the perl (or ruby?) scripts, which
is somewhat trickier.

> the only
> way to figure that out is to check all format paths and take the first
> one that fits; unfortunalty the tetex paths are rather messy so it's
> hard to predict in what permutation of home, usr, share, sys, opt *
> local * tex, TeX, teTeX, whatever * texmf, texmflocal, texmf-local,
> texmf-teTeX, texmf-dis, texmf.local, texmf-whocares * web2c,
> web2c/engine etc etc a format may end up; 

I'm not sure what you mean.  The default TEXMF path for teTeX (and I
think also for TeXlive) is

TEXMF = {!!$TEXMFCONFIG,!!$TEXMFVAR,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFMAIN,!!$TEXMFLOCAL,!!$TEXMFDIST}

where the first three are per-user, the others are system trees.  An
explanation about installing does not need to know whether, for example,
TEXMFLOCAL is called texmf.local or texmf-local or
/usr/local/share/texmf.  The only problem might be that some users
change the order or the trees, but that's not a big problem if we
suggest to use the default path.

> this is further complicated
> by the fact that kpse has to do some guessing about where it's
> configuration files are (web2c, etc, home, nowhere),

This is only a problem if people have more than one texmf.cnf - is this
actually the case?  I don't think I ever heard of that.

> what trees make
> sense, etc etc; and, yes, some of the paths are hard coded in the
> binaries, so relocating is tricky ... isn't it magic that tex still
> runs -)

AFAIK only the search path for texmf.cnf is hard-coded, and that can't
be avoided.  On the other hand, no one ever approached me and requested
a relocation:  What would you want, and in which cases?

TIA, 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  5:53 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 [this message]
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=86hcxufedo.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).