Re: Inter-package interference effect: installing one package upgrades another
Re: Inter-package interference effect: installing one package upgrades another
- Subject: Re: Inter-package interference effect: installing one package upgrades another
- From: Greg Neagle <email@hidden>
- Date: Fri, 19 Dec 2014 15:10:13 -0800
If the installed application contains the same bundle identifier when installed via the suite A package _or_ the suite B package, the Installer _will_ upgrade the application no matter where it is installed if a new package installs that same bundle identifier and has BundleIsRelocatable=true. That's how it works.
-Greg
On Dec 19, 2014, at 3:01 PM, Dave Barker-Plummer <email@hidden> wrote:
> Thanks.
>
> I’m new to this. The bundle identifier identifiers the individual application? If so then, yes, the same application is installed by both suites.
>
> In answer to your question. We would like a person who installs suite A and suite B in non-standard locations (or moves them post install) to be able to upgrade suite A, leaving suite B untouched. If the bundle is not relocatable, then a new copy of suite A will be installed in the install location (if I understand correctly).
>
> We want to be able to upgrade relocated applications. I believe that the OS is supposed to distinguish the suite, i.e. the copy of the application to upgrade, by the package identifier.
>
> — Dave
>
>> On Dec 19, 2014, at 1:22 PM, Greg Neagle <email@hidden> wrote:
>>
>>
>> On Dec 19, 2014, at 10:29 AM, Dave Barker-Plummer <email@hidden> wrote:
>>
>>> My group build two software suites. The applications in these suites overlap — one contains four applications, the other just two of those same applications.
>>>
>>> We are building installers for both packages using pkgbuild and then productbuild (for signing and installation panels).
>>>
>>> The pkgbuild scripts for both packages have different identifiers, and specify BundleIsRelocatable=true, and BundleOverwriteAction=upgrade.
>>>
>>> Now, when we install the smaller suite, one (but not both) of the applications in the smaller package is installed by upgrading the application previously installed by the larger suite. This application in in a different location on disk from the one that we are trying to install, and as mentioned was installed using a different package identifier.
>>
>> But same Bundle identifier (CFBundleIdentifer).
>>
>>>
>>> Does anyone have any ideas, however outlandish, about what might be going wrong, or how to debug the problem?
>>>
>>> FWIW, setting BundleIsRelocatable false has the expected effect.
>>
>> Maybe I'm missing something, but you've described and answered your own problem.
>>
>> BundleIsRelocatable=true tells Installer to upgrade the bundle no matter where it is found on disk.
>> BundleIsRelocatable=false turns off this behavior. So why is setting BundleIsRelocatable=false not the right approach for you?
>>
>> -Greg
>
>
_______________________________________________
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