Issue Feature Rejected

#82559Configurable discovery (path/name) in CommandUtility for tools like python

Stefan Neufeind 09/25/17, 17:38 updated 12/06/17, 09:59

Description

In typo3/sysext/core/Classes/Utility/CommandUtility.php holds list of self::$applications which specify on how to call that binary. So as soon as an extension (like EXT:sphinx) wants to call “python” it has a central point to find a path and possibly also name for that binary.

On some systems the autodetection might fail. Or you might have several versions installed in parallel which have a slightly changed binary name. For older CentOS-version for example there is a python-version 3.4 that can be installed in parallel but “python” is still the original 2.x-version and “python3.4” is the one for python 3.4.

We should invent some way to configure certain commands for which not to use auto-detection but instead provide a fixed path/name. And/or we might want to create a hook where an extension could offer such functionality.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.