ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "amano.kenji" <amano.kenji@proton.me>
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Wed, 17 Aug 2022 13:09:35 +0000	[thread overview]
Message-ID: <JhTgoCa1_rN_kKbbI7-Sh1J0ZUC_sUTJNxb0sl46xrEElsZsPVjqKpzYih6Xs7KUaQNUJGW453G6pH9ojBmSFh5WqRB9Xlec3f3U0qkb1mg=@proton.me> (raw)
In-Reply-To: <6f344278-2a0a-19f2-4fdb-dc0ece76c728@freedom.nl>

* Will TexLive replace its own ConTeXt Mark IV with ConTeXt LMTX?
* context lmtx binary installer archive is not versioned. I can't use unversioned archives in OS packages.
* Is it actually possible to present a separate override file for contextcnf.lua? If not, I would need to patch contextcnf.lua, or contextcnf.lua should support both portable installation and OS-level installation.
* Can you make it easier to make an OS package for ConTeXt LMTX by releasing versioned (source) archives, including BUILD/INSTALL instructions in the versioned archives, and so on? I wish I could just extract a versioned binary archive into certain locations or use GNU autotools or use meson build system which is far better than GNU autotools.

While portable installations can be great for testing bleeding edge features and keeping up with latest development, most of the time, I prefer OS package releases.

------- Original Message -------
On Tuesday, August 16th, 2022 at 4:02 PM, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:


> On 8/16/2022 1:43 PM, amano.kenji via ntg-context wrote:
> 
> > Even if I put the installation in an archive and make a linux package that installs the archive, I still have to modify contextcnf.lua which isn't intended to handle differing system-wide installation paths of various POSIX-like operating systems.
> > 
> > And, I don't really know
> > 
> > * what the variables in contextcnf.lua mean and do.
> > * whether there is a way to override certain variables in contextcnf.lua with another file. A separate override file is going to make it easy for linux distributions to override certain variables in contextcnf.lua.
> 
> mtxrun --generate
> 
> reports all kind of locations where configurations files are looked for
> 
> one can also set environment variables and see what is used
> 
> mtxrun --variables
> mtxrun --expansions
> 
> so there are plenty ways to configure and you can run
> 
> > mtxrun --configurations
> 
> 
> which on my machine gives
> 
> system | resolved | file :
> c:/data/develop/tex-context/tex/texmf-local/web2c/texmfcnf.lua
> system | resolved | file :
> c:/data/develop/tex-context/tex/texmf/web2c/texmfcnf.lua
> 
> indicating that i use an additional configuration file
> 
> there are some boundary conditions:
> 
> - we use mtxrun as runner and that one used luatex as lua engine
> - this means that mtxrun[.lua] has to be in the same path as the binary
> 
> in lmtx we even go a bit further:
> 
> - in lmtx there is mtxrun.lua
> - as well as context.lua
> - there are 'mtxrun' and 'context' binaries that are either copies or
> symlinks to luametatex in the same path
> - this is the same on unix and windows
> 
> in lmtx luametatex is also used as runner for mkiv when installed
> 
> on unix i normally just install the minimal tree and then either add the
> bin path to the path or just run mtxrun fully qualified (actually always
> for the whole system under /data/context)
> 
> Hans
> 
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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-17 13:09 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 [this message]
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
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='JhTgoCa1_rN_kKbbI7-Sh1J0ZUC_sUTJNxb0sl46xrEElsZsPVjqKpzYih6Xs7KUaQNUJGW453G6pH9ojBmSFh5WqRB9Xlec3f3U0qkb1mg=@proton.me' \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    /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).