ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Michal Vlasák via ntg-context" <ntg-context@ntg.nl>
To: "Hans Hagen" <j.hagen@freedom.nl>,
	"mailing list for ConTeXt users" <ntg-context@ntg.nl>,
	"Max Chernoff" <mseven@telus.net>
Cc: "Michal Vlasák" <lahcim8@gmail.com>
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Thu, 25 Aug 2022 02:00:00 +0200	[thread overview]
Message-ID: <CMEO1KJ8S90U.214W2U1GZY6F2@phobos> (raw)
In-Reply-To: <a2fabf09-4944-6eaa-2454-445ec4b4155e@freedom.nl>

On Wed Aug 24, 2022 at 11:32 PM CEST, Hans Hagen wrote:
> On 8/24/2022 10:21 PM, Michal Vlasák via ntg-context wrote:
>
> > Or rather no solution would be needed at all, since the "mtxrun" and
> > "context" wrapper commands and "texmfcnf.lua" files will be probably
> > specific for each packaging target (different directories on different
> > distros, and Unix vs Windows), and thus the matter of packagers. And
> > copying a binary and a directory with runtime files is the usual task of
> > an install step of "package descriptions", so maybe even a Makefile like
> > I had wouldn't be needed.
>
> just a note: the mtxrun[.exe] and context[.exe] commands are not really 
> wrappers but symlinks to the binary luametatex[.exe]  (i didn't test if 
> mtxrun.lua and context.lua can be symlinks but that are to be in the 
> same path in order to be seen)

Yes, sorry I should have been clearer. What is necessary for luametatex
to run a Lua script is to run it with another name (argv[0]). This can
be done with symlinks, or with `exec -a mtxrun luametatex`. And even
mtxrun.lua and context.lua can be symlinks, it works, I used it.

> one can actually use the default texmf.cnf if one sets TEXMF or one of 
> its companions .. they default to be autoparent which is natural for tds

Thanks, indeed the config file sets the paths nicely, so it isn't
necessary to have another file if one sets TEXMF, very nice!

One addition I had was the use of $TEXMFDOTDIR instead of "." as the
first path in most variables, e.g.:

    TEXINPUTS = "$TEXMFDOTDIR;$TEXMF/tex/{context,plain/base,generic}//",

instead of

    TEXINPUTS = ".;$TEXMF/tex/{context,plain/base,generic}//",

I quite like it for adding directories with my macros / bib files etc.
that are not structured as TDS tree, but rather are "flat".

It's originally from TeX Live:

    https://github.com/TeX-Live/texlive-source/commit/f1dfa7b7670fa28451c386fb08e2b32d293741ab

It lists ".//" as another possible use. Could you also add it?

I updated the repo:

    https://github.com/vlasakm/context

Now also `context` is an executable (two more symlinks, so now 4
symlinks and one binary in total). There is no longer a configuration
file by me (the fallback contextcnf.lua gets used or user provides one),
the drawback being that I set some variables in the environment and the
user now can't override them from config file only from environment,
AFAIK. Also

     mtxrun --variables

doesn't work now (maybe other things) though I won't investigate further
for now.

Anyway, thanks for the clarifications and suggestions!

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-08-25  0:00 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 12:03 amano.kenji via ntg-context
2022-08-15 12:12 ` Bruce Horrocks via ntg-context
2022-08-15 12:19   ` amano.kenji via ntg-context
2022-08-15 17:00     ` Bruce Horrocks via ntg-context
2022-08-16 11:43       ` amano.kenji via ntg-context
2022-08-16 16:02         ` Hans Hagen via ntg-context
2022-08-17 13:09           ` amano.kenji via ntg-context
2022-08-17 15:42             ` Hans Hagen via ntg-context
2022-08-18 12:32               ` amano.kenji via ntg-context
2022-08-18 12:56               ` amano.kenji via ntg-context
2022-08-18 13:16               ` Alan via ntg-context
2022-08-18 13:44                 ` amano.kenji via ntg-context
2022-08-18 13:53                 ` amano.kenji via ntg-context
2022-08-22 22:52                   ` Alan via ntg-context
2022-08-18 14:08                 ` amano.kenji via ntg-context
2022-08-18 17:16                   ` Hans Hagen via ntg-context
2022-08-19 12:51                     ` amano.kenji via ntg-context
2022-08-19 13:06                       ` Hans Hagen via ntg-context
2022-08-19 13:03                     ` amano.kenji via ntg-context
2022-08-19 13:11                       ` Hans Hagen via ntg-context
2022-08-19 13:18                         ` amano.kenji via ntg-context
2022-08-20  7:31                           ` Hans Hagen via ntg-context
2022-08-15 13:54   ` amano.kenji via ntg-context
2022-08-15 18:46     ` Alan Braslau via ntg-context
2022-08-16 11:35       ` amano.kenji via ntg-context
2022-08-21 19:13 ` Michal Vlasák via ntg-context
2022-08-22  9:41   ` amano.kenji via ntg-context
2022-08-23  1:11     ` Max Chernoff via ntg-context
2022-08-23 10:15       ` amano.kenji via ntg-context
2022-08-23 10:25       ` amano.kenji via ntg-context
2022-08-24 20:21       ` Michal Vlasák via ntg-context
2022-08-24 21:32         ` Hans Hagen via ntg-context
2022-08-25  0:00           ` Michal Vlasák via ntg-context [this message]
2022-08-23 19:13     ` Aditya Mahajan via ntg-context
2022-08-24 12:30       ` amano.kenji via ntg-context
2022-08-15 21:56 Max Chernoff via ntg-context
2022-08-16 11:28 ` amano.kenji via ntg-context
2022-08-18  0:51 Max Chernoff via ntg-context
2022-08-18  7:31 ` Hans Hagen via ntg-context
2022-08-18 12:00 ` Henning Hraban Ramm via ntg-context

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=CMEO1KJ8S90U.214W2U1GZY6F2@phobos \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \
    --cc=lahcim8@gmail.com \
    --cc=mseven@telus.net \
    /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).