ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <matt@gushee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Path problems w/ MkIV on Arch Linux
Date: Wed, 31 Jul 2013 21:59:40 -0600	[thread overview]
Message-ID: <CABrD0ecL24d0OP9oYeGNEpcACEGbYZuaUyAq4S-rNZsv3UyqQQ@mail.gmail.com> (raw)
In-Reply-To: <51F9827D.30501@wxs.nl>

Thanks, Hans ...

On Wed, Jul 31, 2013 at 3:32 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 7/31/2013 10:51 PM, Matt Gushee wrote:

>> code, so unless there are serious bugs, I want to use the version
>> included with TexLive. At any rate, that's what I currently have and
>> am trying to use. But I am running into issues with files not being
>> found, e.g.:
>
> as a start you could try the distribution from the garden; at least it's a
> good way to figure out if there is something fishy with your system

Okay, I've installed that, and it works fine ... though I had a small
glitch along the way that gives me an idea about what the problem may
be with the TeXLive version. More about that below.

> in the reported 'tree' files in the cache you can check if files like
> context.mkiv are present

They weren't.

> mtxrun --variables
> mtxrun --expansions

Actually, I had already tried that, but I didn't fully understand the
output. Here's an example:

resolvers       | lists | LUAINPUTS
resolvers       | lists |   env: unset
resolvers       | lists |   var: .;$TEXINPUTS;$TEXMF/scripts/context/lua//
resolvers       | lists |   exp:
.;.;{home:texmf,!!selfautoparent:texmf-project,!!selfautoparent:texmf-fonts,!!/usr{/local}/share/texmf,!!selfautoparent:texmf-context,!!selfautoparent:texmf-linux,!!selfautoparent:texmf-dist,!!selfautoparent:texmf-dist}/tex/{context,plain/base,generic}//;{home:texmf,!!selfautoparent:texmf-project,!!selfautoparent:texmf-fonts,!!/usr{/local}/share/texmf,!!selfautoparent:texmf-context,!!selfautoparent:texmf-linux,!!selfautoparent:texmf-dist,!!selfautoparent:texmf-dist}/scripts/context/lua//
resolvers       | lists |   res:
.;.;{/home/matt/texmf,!!./texmf-project,!!./texmf-fonts,!!/usr{/local}/share/texmf,!!./texmf-context,!!./texmf-linux,!!./texmf-dist,!!./texmf-dist}/tex/{context,plain/base,generic}//;{/home/matt/texmf,!!./texmf-project,!!./texmf-fonts,!!/usr{/local}/share/texmf,!!./texmf-context,!!./texmf-linux,!!./texmf-dist,!!./texmf-dist}/scripts/context/lua/

Are the 'selfautoparent' references supposed to be resolved to
specific paths? If so, it certainly appears something was wrong here.

> so no file database is present or the database has not all files

It was the latter, I suspect due to incorrect path settings in the config file.

> does arch-linux use stock texlive or do they adapt it

There are a few, seemingly minor tweaks. There are three patches, all
for luatex:

  poppler-0.20.patch
  fix-fontforge-encoding.patch
  luatex-r4449-radical-rule-thickness.patch

However, these all seem to deal with small graphics/fonts issues and
have no apparent relationship to finding files. There is also a
customized texmf.cnf, but NOT a customized texmfcnf.lua. I think
that's significant.

I said above that I ran into a minor problem when I installed the
Contextgarden package. What happened was that I saw two ../bin
directories: /opt/context/bin and /opt/context/tex/texmf-linux/bin .
At first I thought /opt/context/bin was meant to be used, so I added
both directories to my PATH [/opt/context/bin was first]. But that
produced errors. Then I removed /opt/context/bin from PATH, and
everything was fine. So I think I see what's going on: since many of
the path settings in texmfcnf.lua use 'selfauto*' variables, and
correct resolution of those depends on where the executables are
located. So I suspect that the default config file that comes with
ConTeXt in TeXLive assumes that the executables are ... I'm not sure
where, but somewhere other than /usr/bin . I could probably fix that,
but it would take me a while to figure out the correct values.

Anyway, at this point I'm seriously thinking about just forgetting
TeXLive and using the standalone ConTeXt package. I doubt I'll be
using any other TeX packages in the near future, and I'd rather spend
time creating documents than tinkering with config files. Is there
anything in TeXLive that's particularly useful with ConTeXt, that is
not included in the ConTeXt package?

Anyway, many thanks for your prompt attention!

--
Matt Gushee
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2013-08-01  3:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 20:51 Matt Gushee
2013-07-31 21:32 ` Hans Hagen
2013-08-01  3:59   ` Matt Gushee [this message]
2013-08-01  5:52     ` Aditya Mahajan
2013-08-01  9:40     ` Hans Hagen
2013-07-31 21:50 ` Marco Patzer

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=CABrD0ecL24d0OP9oYeGNEpcACEGbYZuaUyAq4S-rNZsv3UyqQQ@mail.gmail.com \
    --to=matt@gushee.net \
    --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).