| Well, before I revert to a DMG file, I would likely play with the “Resources” folder a little bit. You can add a zip archive of the Modules folder to the Resources folder of a package, and then script the expansion and move.
Can you run a diff compare on the source files and the bundles after deployment? How are you creating the Modules folder, could it have odd permissions issues? What if you modify the package to deploy to a folder with looser permissions, such as /Users/Shared, or to an external volume?
I don’t know enough about app bundles created through Director, but if it’s not permissions, the next issue I would be concerned about is bundle-bit (the apps behaving like folders, not bundles), or possibly even resource fork type issues. You mentioned DMG distribution, have you tested that? Does flat file copy (such as drag and drop, but a COPY, not a MOVE) preserve functionality?
On Apr 8, 2015, at 10:03 AM, SOI Technical Support < email@hidden> wrote:
Thanks for the response Conor. Permissions was my first guess as well, but I think I've exhausted that avenue. The apps fail to launch even on the system that created them. On that system I can go to the directory that I'm creating the package from, and launch the apps. But if I run the pkg installer on that same system, and go to the directory under applications and try to launch the newly installed copy of that file, it won't launch.
I've fiddled with the permissions set for the apps and subdirectory in Packages, even setting full unsecure rwx across the board for testing purposes, and still they don't launch. Most of the files were set to root:admin, but changing to root:staff didn't seem to have an effect.
I appreciate the tips on creating multiple component packages, but if I can't get this working, will probably just fall back to distributing in a dmg file. These old Director apps' days are numbered anyway, will eventually rewrite them in a better language and build them into a single application.
|