[Context] latest LuaTeX
![](https://secure.gravatar.com/avatar/6114858d84b0f40cf715f12237ab67a1.jpg?s=120&d=mm&r=g)
Hello, The experimental branch of minimals is not quite functional: since rsync doesn't work the way I would want it to work, the initial idea to provide patches in experimental branch only is not really usable. I would like to collect some ideas how to match context version (current, beta, (alpha - not too important), experimental) with the proper luatex version. First question (for Taco): pdftex and xetex are probably OK. We need luatex, do we need some flavour of experimental metapost versions as well? Second question: I have set up rsync to provide current/luatex (latest beta) current/pdftex (svn) current/xetex (svn) current/metapost (latest beta) latest/luatex (svn) latest/pdftex (svn) latest/xetex (svn) latest/metapost (svn) We can probably drop latest/pdftex and latest/xetex, Taco should tell about metapost. The automatic procedure builds the first four. We probably need to compile latest/luatex by default as well. But then the next question ... how to match context version with the right luatex version? My idea is that whenever one requests --context=experimental then luatex binary could be taken from experimental/bin/luatex/platform/ instead of current/bin/luatex/platform/, but what about ConTeXt beta and what to do when Taco releases a new luatex beta and Hans doesn't release new ConTeXt "current"? Hans - I need some of your ideas here. At the moment both ConTeXt current and beta on the garden are freezed (do not match the version on PRAGMA) in order not to fail completely since we have no latest luatex binaries in the repository. Suggestions? Your release plans for the near future? Mojca PS: I will be away for the next two weeks. There might be some internet connection, but I'm not sure about it.
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Mojca Miklavec wrote:
First question (for Taco): pdftex and xetex are probably OK. We need luatex, do we need some flavour of experimental metapost versions as well?
No, I don't think so. Luatex has mplib embedded, and mkii is not a suitable testbed for metapost development testing, so just don't track metapost developments except for proper betas and official releases.
The automatic procedure builds the first four. We probably need to compile latest/luatex by default as well.
But then the next question ... how to match context version with the right luatex version?
This is a tricky probem right now. Maybe Hans could add a \requiredluatexversion in context.mkiv ?
Hans - I need some of your ideas here. At the moment both ConTeXt
Hans is on the road today ... Best wishes, Taco
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Mojca Miklavec wrote:
Hello,
The experimental branch of minimals is not quite functional: since rsync doesn't work the way I would want it to work, the initial idea to provide patches in experimental branch only is not really usable.
I would like to collect some ideas how to match context version (current, beta, (alpha - not too important), experimental) with the proper luatex version.
First question (for Taco): pdftex and xetex are probably OK. We need luatex, do we need some flavour of experimental metapost versions as well?
probably not, metapost does not change that much wrt functionality
Second question: I have set up rsync to provide current/luatex (latest beta) current/pdftex (svn) current/xetex (svn) current/metapost (latest beta) latest/luatex (svn) latest/pdftex (svn) latest/xetex (svn) latest/metapost (svn) We can probably drop latest/pdftex and latest/xetex, Taco should tell about metapost.
fyi: mkiv does not use the metapost binary, and mkii mp code does not change that much
The automatic procedure builds the first four. We probably need to compile latest/luatex by default as well.
But then the next question ... how to match context version with the right luatex version?
for both always use the latest -)
My idea is that whenever one requests --context=experimental then luatex binary could be taken from experimental/bin/luatex/platform/ instead of current/bin/luatex/platform/, but what about ConTeXt beta and what to do when Taco releases a new luatex beta and Hans doesn't release new ConTeXt "current"?
in many cases context will just work, unless we have drastic new things, like math
Hans - I need some of your ideas here. At the moment both ConTeXt current and beta on the garden are freezed (do not match the version on PRAGMA) in order not to fail completely since we have no latest luatex binaries in the repository. Suggestions? Your release plans for the near future?
i'd say: experimental == beta (from ftp) and latest luatex; these always match and i don't expect taco to release luatex's that make context fail misserably
PS: I will be away for the next two weeks. There might be some internet connection, but I'm not sure about it.
you being offline for two weeks? i'm sure you'll manage to find a (hot)spot have a nice time Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Hans Hagen
-
Mojca Miklavec
-
Taco Hoekwater