Re: Error running a pkg on 10.3.9
Re: Error running a pkg on 10.3.9
- Subject: Re: Error running a pkg on 10.3.9
- From: Bill Coderre <email@hidden>
- Date: Wed, 03 Nov 2010 11:12:31 -0700
There were a lot of small reasons to go flat. One reason is that a single-fork single-file installer package is that it's much easier to ship and store on non-Mac OS file systems without damage. Another is that it makes applying a digital signature simpler. There were others I'm not recalling at this moment.
You can look inside packages by doing
pkgutil --expand MyPackage.pkg MyPackage.pkgsrc
Pacifist also is pretty happy to show the insides of a flat package.
There is also a QuickLook plugin that someone wrote: http://www.quicklookplugins.com/2008/03/02/suspicious-package-updated-to-v11/
On Nov 3, 2010, at 5:32 AM, Michael Stauffer (Circular Logic) wrote:
> Yes, thanks. I double-checked the min install OS, and it was 10.5 for
> the meta/main package. I'd only set it to 10.3 for the sub-packages.
> Thanks!
>
> I wonder why apple changed to a flat package. It use to be helpful
> sometimes to look in a package bundle when the install wasn't going
> well.
>
> Cheers
>
>> -----Original Message-----
>> From: Iceberg-Dev [mailto:email@hidden]
>> Sent: Wednesday, November 03, 2010 4:40 AM
>> To: Michael Stauffer (Circular Logic)
>> Cc: email@hidden
>> Subject: Re: Error running a pkg on 10.3.9
>>
>>> Hi,
>>>
>>> I've created a .pkg with PM 3 on 10.5. I set the pkg's minimum OS
>>> version as 10.3. It works fine on 10.5 and 10.6, but when I run on
>>> 10.3.9 (PMac G4), I get the error "the bill of materials for this
>>> package was not found".
>>
>> Is the minimum OS version a requirement or the target OS?
>>
>>> The pkg contains two other packages. PM used to make a metapackage,
>>> but
>>> when I loaded the PM project into PM 3, it now builds only as a .pkg,
>>> not .mpkg. Is this part of the problem?
>>>
>>> Also, the final output pkg is a file, not a bundle, which is also
>>> new to
>>> me. The sub packages I built with PM 3 are .pkg files too, but
>>> bundles.
>>> Is there something I set in one project but not the other that I
>>> haven't
>>> found?
>>
>> If you get a file instead of a bundle, this could mean that the
>> target OS has changed and is now 10.5 and you are building a flat
>> package/distribution instead of a bundle package/metapackage.
>>
>>
>>
>>
>
> _______________________________________________
> 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