Okay, TexLive will get ConTeXt LMTX.
If TexLive was the official way to ship stable versions of ConTeXt, I am okay with having TexLive ConTeXt as a system package and using ConTeXt LMTX portable installer for testing bleeding edge features.
Still, there are a few ways to ship latest changes in ConTeXt LMTX as a linux package.
1. If I could just download a few binary archives and extract/unzip them into certain directories and modify contextcnf.lua in my package build script and be done, I can publish linux packages.
2. If https://github.com/contextgarden/context-mirror/ contains build instructions as a document, then I can make linux packages against recent git commits. This is better than 1 because linux distribution maintainers can build packages for each CPU architecture.
app-text/context would not be able to exist together with app-texlive/texlive-context because both are OS packages.
------- Original Message -------
On Wednesday, August 17th, 2022 at 3:42 PM, Hans Hagen
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 -----------------------------------------------------------------