For future reference, the "execute" permission for a folder is the ability to access it. In standard unix, folders don't have any possible execution in the normal sense of the word.

> For future reference, the "execute" permission for a folder is the ability to
> access it. In standard unix, folders don't have any possible execution in
> the normal sense of the word.

You are of course correct. What a shame Apple do not let you access and use this flag on folders in Workgroup Manager to configure access to directories shared by Mac OS X Server (one could do it via the Terminal but this is not 'The Macintosh Way').

That makes sense.

Nevertheless, I did say "the ownership and permissions of all files in the package" and "adding the 'execute' permission to the whole folder, recursively."

There is probably a more correct way to describe what I did, which was to ensure that all the _files_ in the application package were executable by adding the execute permission to the whole folder, recursively (i.e. the entire directory tree) that constitutes the application package/bundle.

Thanks for clarifying that fact, though. :o)