Robin
If antixcc.sh used $(which …) to identify the paths where tools are installed instead of hard-coding them, it wouldn’t be an issue.
True, and some of the Control Centre entries I had added in the past actually have these
if which … >/dev/null; then
…structures. But it turned out this slows down the startup of antiX Control Centre remarkably, so I dropped this approach again and returned to hard coded paths. Please consider: For each single entry this which must be processed on startup… That might not be relevant for fast machines, but on weak ones this is not acceptable. Or am I wrong here and running a hundred times which wouldn’t have a noticeable impact on the startup time consumption of antiX Control Centre?
Fixed control centre sent to repos
Many many thanks for this quick fix!
Windows is like a submarine. Open a window and serious problems will start.