As of 99a98bd we have some rudimentary check whether the engine executable is available. This has two problems:
It prevents engine names to differ from the name of the executable.
It does not extend to extensions.
It does not allow to check for more than one dependency per engine.
So, implement is in a proper way! That is, main script as well as every engine and extension can have a list of binaries that have to be available. ltx2any should be robust against missing requirements and inform the user clearly what they need to install.
As of 99a98bd we have some rudimentary check whether the engine executable is available. This has two problems:
So, implement is in a proper way! That is, main script as well as every engine and extension can have a list of binaries that have to be available. ltx2any should be robust against missing requirements and inform the user clearly what they need to install.
Nota bene: check gems, too.