unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Missing native-search-path for texlive
Date: Mon, 30 Nov 2015 15:20:06 +0100	[thread overview]
Message-ID: <20151130142006.GA3964@debian> (raw)
In-Reply-To: <878u5fab63.fsf@gnu.org>

On Mon, Nov 30, 2015 at 02:07:00PM +0100, Ludovic Courtès wrote:
> It ‘TEXMF’ really a search path, or is it rather a variable that should
> point to a single directory?

It is a variable that works like a search path, but with a special syntax:
/gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015/share/texmf-dist/web2c/texmf.cnf
contains a line
TEXMF = {$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFLOCAL,!!$TEXMFDIST}

The context binary itself is the following shell script:
#!/gnu/store/ibpm6n6706yimzr3967krkxi2ibxq5yh-bash-4.3.39/bin/bash
export TEXMFCNF="/gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015/share/texmf-dist/web2c"
exec -a "$0" "/gnu/store/i11ykp24wbgq2lfz7gcz2v0f5h3sg7dg-texlive-bin-2015/share/texmf-dist/scripts/context/stubs/unix/context" "$@"

The variable TEXMFCNF gives the directory where texmf.cnf is to be found;
this configuration file contains the definition of TEXMF (composed of the
other variables). So one would expect the wrapper to be already in place,
provided by texlive.

The call in the last line is to the following shell script:
#!/gnu/store/311nvir0pz1mhf0mgsmfrw00qfj7yq0j-bash-4.3.39/bin/sh
mtxrun --script context "$@"

"mtxrun" is the following shell script:
#!/gnu/store/ibpm6n6706yimzr3967krkxi2ibxq5yh-bash-4.3.39/bin/bash
export TEXMFCNF="/gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015/share/texmf-dist/web2c"
exec -a "$0" "/gnu/store/i11ykp24wbgq2lfz7gcz2v0f5h3sg7dg-texlive-bin-2015/bin/mtxrun" "$@"

Again, this is a wrapper setting TEXMFCNF.
The mtxrun binary is a lua script.

The following lines in the script could be of interest:
resolvers.criticalvars=allocate { "SELFAUTOLOC","SELFAUTODIR","SELFAUTOPARENT","TEXMFCNF","TEXMF","TEXOS" }
resolvers.luacnfname="texmfcnf.lua"

I suppose that the normal behaviour will then be to look for the file
texmfcnf.lua in the directory given by TEXMFCNF, set by the wrapper scripts.
This file seems to be a lua script that is equivalent to texmf.cnf.
We modify texmf.cnf to point to the correct directories, using a single
substitute:
              (substitute* texmfcnf
                (("TEXMFROOT = \\$SELFAUTOPARENT")
                (string-append "TEXMFROOT = " share)))
which results in the line
TEXMFROOT = /gnu/store/gb4y83bvcpkvdmz0dvi9rp507kbdbr5x-texlive-texmf-2015/share
All further variables depend on TEXMFROOT.

So we should probably also modify texmfcnf.lua in a similar way.
Unfortunately, it contains a lot of selfautoparent and selfautodir;
we should replace them all at the same time.

I can propose a patch later.

Andreas

  parent reply	other threads:[~2015-11-30 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  1:41 Missing native-search-path for texlive Alex Vong
2015-11-30 13:07 ` Ludovic Courtès
2015-11-30 13:30   ` Alex Vong
2015-11-30 14:20   ` Andreas Enge [this message]
2015-11-30 16:37     ` Alex Vong
2015-12-30 10:32     ` Andreas Enge

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151130142006.GA3964@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).