One idea I had is that for each of the unix command line tools that is a dependency (e.g. as listed in README.md) - you might use each of those commands 'bare' with no path and then put in your instructions that the user's path needs to include each dependency. In fact, early on in the script you could test for each of those and complain..
This would make your script work in a much wider variety of weird os configurations...
One idea I had is that for each of the unix command line tools that is a dependency (e.g. as listed in README.md) - you might use each of those commands 'bare' with no path and then put in your instructions that the user's path needs to include each dependency. In fact, early on in the script you could test for each of those and complain..
This would make your script work in a much wider variety of weird os configurations...