Re: IFPkgFlagInstalledSize not working on OS X < 10.4?
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On jeudi, mars 9, 2006, at 12:36 AM, Rob Hudson wrote: On vendredi, mars 3, 2006, at 05:54 PM, Rob Hudson wrote: Hello, Stupid idea of the day: 1. Create a package A with the media content. 2. Create a package B installing nothing. 4. Add your postflight script in package A. The quick test I made on 10.2.8 tend to prove it just works. Probably. I don't have a 10.3 system so I can't test. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... On Mar 3, 2006, at 2:18 PM, Stéphane Sudre wrote: We are creating an installer for an educational program and are having some trouble. Our installer works fine on 10.4, but when we test it on 10.2 or 10.3 it is not displaying the correct size that we put into the Info.plist file for key "IFPkgFlagInstalledSize". Is this key supported on older OS X platforms? If so, where else can we look to correct this? Some more information: We are attempting to create a hybrid install on the same CD for both Mac and Windows. Since this program contains media content and is large, if we package the media content in the installer for both platforms it will not fit on a single CD. We are using a postflight script to copy the media files to the selected destination. On the Windows side, we are using NSIS installer and doing effectively the same thing. The short version is that the media content is not in the .pkg directory, but in a directory at the root level of the CD. Does the Mac installer try to calculate the size itself, and thus the media content isn't part of the calculation? Thanks for any guidance and help. 3. Take the Archive.pax[.gz] file from package B and use it to replace the one in package A. 5. Now you can run an installation of package A. The installer is looking at the .bom to know how big is the installed media. And when the installation runs, it's not installing anything from the Archive.pax.gz. So your postflight script can just do its stuff. My $0.02 In testing, we found that this isn't working on 10.3. We get the following error during install: [snip] Mar 8 15:03:43 : Running task: /System/Library/PrivateFrameworks/Installation.framework/Resources/pax Mar 8 15:03:46 : ERROR:Could not write file. - pax: WARNING! These patterns were not matched: - [snip] Mar 8 15:03:49 : Install Failed Mar 8 15:03:49 : Error detected Mar 8 15:03:49 : Name: NSGenericException Mar 8 15:03:49 : Reason: Some files for Sizes A may not have been written correctly. (code 1) Mar 8 15:03:49 : Aborted install. [snip] Could this be related to the Archive.pax.gz file? This email sent to site_archiver@lists.apple.com
participants (1)
-
Stéphane Sudre