The problem was the `[ ! -f "${bin_loc}" ]` check. `command -v` does not
necessarily return an absolute path (it can just return the name of the
command for builtins) and this is what happened for 'printf'. Thus, the
`[ ! -f` check failed.
This check doesn't really make sense. If `command -v $binary` doesn't
fail you're good to go, it doesn't really matter where $binary is
located.
On a vanilla invocation, `wine-pyinstaller.sh` will prepare a
Python-3.5 environment under Wine-3. The current requirements to run
the script are following:
1. p7zip-16.xx
2. Wine-3.xx
3. WinPython-3.5.4
All of [1-3] are available in Debian Testing or Ubuntu Bionic
repositories.
P.S.
WinPython was used since official Python-3.5.4 from Python.org wont
run under Wine. Python-3.6 is not supported yet under Wine-3.xx.
