Dear Dalyoung, I looked again at what is happening when installing LuaMetaTeX under MacOS 10.15. In fact, even after completely disabling Gatekeeper and SIP (System Integrity Protection), when running sh install.sh if the three files sitting in ~/context-os-64/bin/ mtx-install.lua mtxrun mtxrun.lua are write protected then the installation cannot proceed. And if they are not, they are overwriiten with something with the same names but which are binaries. And if this is the case then the installation does not proceed for some other reasons. I don't understand why this is the case… If you can go back to MacOS 10.14 that would be nice, but otherwise as Floris suggests in his response, maybe we have to abandon MacOS in the near future… Best regards: OK

On 8 Dec 2019, at 09:12, Jeong Dal wrote:

Dear Hans and Otared,

Thank you again for your attempt to find a solution.

Catalina(MacOS 10.15.1) prohibits an unauthorized program run. So I have to allow the execution of “mtxrun” manually in the preference.

Since "mtxrun —generate” ends with the message “unknown script mtxrun-context.lua or mtx-mtxrun-context.lua”, I tried to locate it in the finder. There is one in a folder installed by MacTeX(TeXLive), but not in “ConTeXtLMTX”.

As you said, many files are not copied during the installation. I’ll try to understand what is going on, but it would be very hard to find a solution by myself.

I have to use old ConTeXt for a while.

Thank you again.

Best regards,

Dalyoung

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________

On 08/12/2019 17:35, Alan Braslau wrote:

...

but otherwise as Floris suggests in his response, maybe we have to abandon MacOS in the near future… No, simply we need to adapt our procedures (installation scripts) to be compatible with MacOS policy.

That is indeed part of the issue: these platforms want You to move away from the things that worked before and force you into closed areas that'll make you depend on them. Its a pattern and a waste of energy that could be better spend... (but one cannot force people to their luck ;-) .F