context team mailing list archive
-
context team
-
Mailing list archive
-
Message #00064
switching to the next luatex "generation"
Hello,
Hans sent me a patch to fix behaviour of the latest LuaTeX (that I
still need to test). Should we wait? Should we patch the otf files and
switch to the latest luatex? (linux-ppc and solaris would lag behind
until we get the new binaries, but that doesn't seem too critical)
Should I wait for the "big package" of changes?
The main problem is now also the "current" branch of ConTeXt. If we
switch to the new LuaTeX, then current ConTeXt will stop working
properly with mkiv.
On the other hand: I'm still looking for a better way to deal with
such incompatibilities.
- There is a way to switch to an older ConTeXt, but that doesn't
really help since LuaTeX changes too fast.
- There is experimental branch that is not fully functional (but could
be made functional, I'm only not sure what binaries to commit there).
Some ideas or discussions would be welcome.
- One could misuse a different server or a different subdomain to put
"more experimental stuff" there and then only sync if there have been
no problems observed for more than three days
- One could put the whole texmf-whatever tree with all the modules
under version control; one looses the possibility to choose modules,
but at least the option to roll back in time would be there
Any suggestion welcome.
Mojca
Follow ups