Permissions and Configuration question about creating a package of a script in Composer

@psherotov If the script is going to be called from a LaunchAgent then the calling context will be the logged in user and you'll want to set the following permissions (this is an excerpt from a post install script):

@sdagley Thank you for the information! Forgive my ignorance but what does the /usr/sbin/ and /bin/ mean in the context of your snippets? I see it a lot, for me I usually cd to the directory and then type in the commands or drag and drop the script into terminal and then run the commands. I'm sure I'm missing something, I just don't know what :-)

@psherotov I used the full path for the executable that will be run when the chown or chmod commands are used. The built-in shell command 'which' will return the path to a command (e.g. 'which chown' returns '/usr/sbin/chown')

As an aside, if you're using Composer, you can also set file ownership/permissions in there before you build the pkg/dmg.

I just dragged one in to show the checkboxes on the lower, right corner.

Am I missing something – is the only way in Composer to set ownership/permissions to set them individually for each file and folder or is there a way to set them recursively on a folder and have them inherited by subfolders and files within?

@J_Morgan To replicate permissions in Composer click the ... icon to the right of the permissions grid:  

Perfect, thanks!