Re: Packages installer with multiple .app files, only one will launch after install.
Re: Packages installer with multiple .app files, only one will launch after install.
- Subject: Re: Packages installer with multiple .app files, only one will launch after install.
- From: Conor Schutzman <email@hidden>
- Date: Wed, 08 Apr 2015 08:55:13 -0700
Sounds like incorrect permissions are being specified for the bundles when importing them into the Packages project. My guess is that the files on the development system are owned by a specific user (such has the user that created them), and that user doesn’t exist on the system that the files are being deployed to. If that’s the case, I would start by trying to use more global permissions such as being owned by root with a group of wheel, admin, or staff. Another option would be to install them into a temp directory, and then have a postnatal script move them to a specific user (such as the current console user’s) home folder, and set them to be owned by that user.
I’ll also add (separately, as I doubt it will address the issue at play), that it may make sense to create multiple component packages, to provide additional install options. One example of this would be to install the main app with one component, and then the modules folder (if not each individual module) as a separate component. You could then wrap all of those various components into a single distribution package with various custom install choices. This would have the additional benefit to allow you to test individual component packages independent of the larger installation process.
Clear as mud?
—
Conor Schutzman
email@hidden
> On Apr 8, 2015, at 8:35 AM, SOI Technical Support <email@hidden> wrote:
>
> I've created a few distributions using Packages, and thought everything went smoothly.
>
> Come to find out though, as some of the distributions contain more than a single .app executable, they are broken upon install. In particular, I have a distribution that installs a folder in the Applications directory, which has a main app file in it, and then a folder called "Modules", within Modules there are several small app files that are launched from within the main app as needed.
>
> These apps were all created in Adobe Director 12, they work when testing in the development environment, and they work when opening the app files manually in the filesystem, but after installing with a Packages created pkg file, the main app will launch, but none of the other app files will.
>
> I've test with another distribution that has a main app and then a "help" app, both in same directory. The main app launches, but the help app does not.
>
> I've fiddled with permission settings within Packages, and everything else I could think of, with no luck. Any advice as to what might be going wrong, or if I should be setting up Packages in a specific way to handle installing multiple app files would be appreciated.
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Installer-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden