ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "amano.kenji" <amano.kenji@proton.me>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Wed, 17 Aug 2022 17:42:18 +0200	[thread overview]
Message-ID: <31267acd-415c-bad0-e232-14ab3c145ea9@freedom.nl> (raw)
In-Reply-To: <JhTgoCa1_rN_kKbbI7-Sh1J0ZUC_sUTJNxb0sl46xrEElsZsPVjqKpzYih6Xs7KUaQNUJGW453G6pH9ojBmSFh5WqRB9Xlec3f3U0qkb1mg=@proton.me>

On 8/17/2022 3:09 PM, amano.kenji wrote:
> * Will TexLive replace its own ConTeXt Mark IV with ConTeXt LMTX?

at some point we will switch to lmtx and mkiv is than just there and can 
be used but basically it is frozen (already for a while, apart from fixes).

> * context lmtx binary installer archive is not versioned. I can't use unversioned archives in OS packages.

at some point (all depends on time and effort and ...) the source wil be 
part of the context distribution so then one can compile

> * 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.

you can put one in texmf-local (as the mtxrun --generate i posted trace 
shows)

> * 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.

there is a github repository for the tex stuff and have no experience 
with all that versioning / release / os packaging stuff (couldn't test 
it anyway and continuously adapt to teh subtle differences in 
distributions and os's) ... we just post zips (already for decades) but 
anyone is free to come up with such instructions (e.g. aditya did some 
for arch)

anyway, lmtx is still kind of experimental and at some point 
installation will move to the garden (not much is needed, just a web 
server) and the packaging scripts are / will be in the distribution  .. 
there are no dependencies (and we keep it that way: self contained bins)

sorry, i just can't spent time on all the possible variant ways of 
installation .. that is up to volunteers

> 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.
I never use an os tex release .. who knows whaty has been done with it 
.. esp when one has a long term workflow (e.g. fonts can change)

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
___________________________________________________________________________________

  reply	other threads:[~2022-08-17 15:42 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 [this message]
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=31267acd-415c-bad0-e232-14ab3c145ea9@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    --cc=j.hagen@freedom.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).