From pegasus-users slack

 
thanks for working on the fix for the transformation confirmation catalog in the dax. However, I think there is a more fundamental issue here. It seems as though pegasus is using hardcoded paths for specific programs that it needs to run a workflow; e.g., tar, cp, maybe others that we’re unaware of. Those paths apparently are hardcoded for linux systems, which is why we’re running into issues when running on MacOS. Shouldn’t pegaus be using the PATH file (basically, run which) to get the paths for those exectuables? That would be a more stable solution than having to specify a transformation catalog to basically undo the hardcoded paths.
 
Karan Vahi - Pegasus StaffKaran Vahi - Pegasus Staff  Friday at 1:01 PM

yes we do have logic to pick executables from PATH. i need to revisit the code for which executables we pick from the path