In the 11sp2 release, command-line utilities have to be specified for some common functionality. As a stopgap measure before more native OS X interfaces are created, it would be nice to have the following bundle actions:

1) An "OS X application launch" action that already explicitly called the "/usr/bin/open" binary and only required the user to place a path to the OS X application bundle in order to work properly.

2) Along the same lines, an "OS X package install" action that explicitly called "/usr/sbin/installer" and only required a path to an OS X .pkg bundle.

3) An extension to the "scripts" action that includes a dropdown list of the scripting environments that are included with OS X (i.e. php, perl, the shells, python, ruby) and will automatically call the standard system path to them if that dropdown is selected. It should also include an option to specify another path, since many users install other scripting environments or alternate versions of the standard environments.

by: Johnnie O. | over a year ago | Application Mgmt