Re: How does installer decide what to install
Re: How does installer decide what to install
- Subject: Re: How does installer decide what to install
- From: Alexander Cohen <email@hidden>
- Date: Wed, 20 Oct 2010 20:16:54 -0400
Heres what i've got. I have a metapackage create with PackageMaker 2.0 that contains 4 packages also created with 2.0. The version numbers of all packages and metapackes have been bumped up and the identifiers have not changed. When i run the old metapackage over the new one, it just runs through as an upgrade and installs everything. If i run each of the old packages over the new install, each package wont let me install and says a newer version already exists on disk. This is the right behavior but users wont install like that. So why wont the old metapackage either not replace anything on disk or just tell the user that there is a newer version disk.
thx
AC
On Oct 20, 2010, at 3:34 PM, Iceberg-Dev wrote:
>
> On Oct 20, 2010, at 7:49 PM, Alexander Cohen wrote:
>
>> Hello,
>>
>> Is there a reference anywhere that explains in detail how install decisions are made by Apple's installer? I'm looking for info on what items it looks at to make the informed decisions it makes ( plists, bundle identifiers, receipts, ... ).
>>
>> The reason i'm asking is because we have some old software that always gets installed over newer versions of the same software but the installers are built form the same project and the versions have been bumped
>
> If the bundle identifiers of the packages are different, it can be a reason why an older version can be installed over a newer one.
>
>
>
> _______________________________________________
> 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