March 2006 - Installer-dev - lists.apple.com

Re: Can you omit stock Apple installer sections?
by Christopher Ryan 04 Mar '06

04 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com There is no supported way to omit these two sections. Chris -nh ---- Nathan Herring MacBU SDE/Development _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/ryanc%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… If I put an InstallerSections.plist into a basic metapackage's Contents/Plugins folder and put in an order which omits Introduction and FinishUp, the installer keeps these, just moving them to the end. Is there no way to omit Apple sections? This email sent to ryanc(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: IFPkgFlagInstalledSize not working on OS X < 10.4?
by Rob Hudson 04 Mar '06

04 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com That did the trick! Thanks for the reply. 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. My $0.02 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… On Mar 3, 2006, at 2:18 PM, Stéphane Sudre wrote: 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. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Automating PackageMaker CLI with Preserve Resource Forks option
by Stéphane Sudre 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, mars 3, 2006, at 09:07 PM, Robert Simutis wrote: Could be because of bugs in SplitFork. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Thanks all for your responses and suggestions. I ended up modifying the "/private/etc/sudoers" file on my build machines to do the following: username ALL=NOPASSWD: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker username ALL=NOPASSWD: /usr/sbin/chown *.pkg, /usr/sbin/chown *.mpkg, /bin/chmod *.pkg, /bin/chmod *.mpkg This allows the build script to run "PackageMaker" with sudo -- however the file ownership becomes root as a result, and thus it must be followed up with "sudo chmod" and "sudo chown" commands in order to restore permissions. It's still a puzzle why "sudo" is needed at all for resource forks but not data forks, but at least this gets around the automated builds problem. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Can you omit stock Apple installer sections?
by Stéphane Sudre 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, mars 3, 2006, at 11:01 PM, Nathan Herring wrote: Of course, there is some way. But the solution is really ugly: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… If I put an InstallerSections.plist into a basic metapackage's Contents/Plugins folder and put in an order which omits Introduction and FinishUp, the installer keeps these, just moving them to the end. Is there no way to omit Apple sections? "Patch Installer.app from a plugin you add in the Contents/Plugins folder of your package/metapackage" This email sent to site_archiver(a)lists.apple.com

1 0

Re: IFPkgFlagInstalledSize not working on OS X < 10.4?
by Stéphane Sudre 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com 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. My $0.02 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… 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. This email sent to site_archiver(a)lists.apple.com

1 0

Can you omit stock Apple installer sections?
by Nathan Herring 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcY/DfUifi/gRoeeQ1qilxOUzLdWIw== Thread-topic: Can you omit stock Apple installer sections? If I put an InstallerSections.plist into a basic metapackage's Contents/Plugins folder and put in an order which omits Introduction and FinishUp, the installer keeps these, just moving them to the end. Is there no way to omit Apple sections? -nh ---- Nathan Herring MacBU SDE/Development _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE: Automating PackageMaker CLI with Preserve Resource Forks option
by Robert Simutis 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcY+/hdKezWpxUART4eVAS0rp0hmkA== Thread-topic: Automating PackageMaker CLI with Preserve Resource Forks option _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

IFPkgFlagInstalledSize not working on OS X < 10.4?
by Rob Hudson 03 Mar '06

03 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hello, Thanks for any guidance and help. -- Rob Hudson Senior Programmer Oregon Center for Applied Science http://www.orcasinc.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… 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? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Upgrade installer info?
by Bill Coderre 01 Mar '06

01 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Apple does this all the time, for instance, iWeb_101.pkg On Mar 1, 2006, at 12:10 PM, Peter Bierman wrote: At 11:17 AM -0800 3/1/06, Nathan Herring wrote: I can create a installer package for say the 1.0 version of my product suite. Beyond a few applications, there's a large number of supporting frameworks and files. Great. Now, I need to edit two of the largish applications for a 1.0.1 release. In the old days, we could use VISE and patch the two largish applications, probably using whatever binary diffing format they have. Is there any such process for the Apple Installer? Is there a way to patch rather than overwrite? Is creating the upgrade installer just a matter of having a sparse installation folder and archiving that, or are there other instructions? There isn't explicit support for this, but we're considering it for a future release. The workaround is pretty simple: just create a package that the installer won't realize is an 'upgrade' of your old package, and only put the modified files in the new package. That gives you a 'sparse' package, and the installer won't delete any of the missing files as long as it doesn't match your package to the older version by CFBundleID or package name. The only downside is that if there are files that need to be deleted during upgrade, you have to figure out what they are, and you deal with them "manually." Apple does this by using various "diff" commands to determine the list, and then including a script that takes a list of files/folders to be deleted. This can be quite annoying if the list is in flux due to ongoing development. Alas. Note also that Apple endeavors to make the "update" be 100% identical to the "fresh install" so as to avoid surprises later. Nib files are especially likely to cause problems. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Upgrade installer info?
by Christopher Ryan 01 Mar '06

01 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com which had: Chris -pmb _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/ryanc%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… One other way to do this is to build a sparse package of 1.0.1 and have a file in the Resources folder named "Hints.plist" <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http:// www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <array> <array> <string>/*</string> <string>dontobsolete</string> </array> </array> </plist> This will instruct the installer not to remove items that existed in the old package and not the new package. At 11:17 AM -0800 3/1/06, Nathan Herring wrote: I can create a installer package for say the 1.0 version of my product suite. Beyond a few applications, there's a large number of supporting frameworks and files. Great. Now, I need to edit two of the largish applications for a 1.0.1 release. In the old days, we could use VISE and patch the two largish applications, probably using whatever binary diffing format they have. Is there any such process for the Apple Installer? Is there a way to patch rather than overwrite? Is creating the upgrade installer just a matter of having a sparse installation folder and archiving that, or are there other instructions? There isn't explicit support for this, but we're considering it for a future release. The workaround is pretty simple: just create a package that the installer won't realize is an 'upgrade' of your old package, and only put the modified files in the new package. That gives you a 'sparse' package, and the installer won't delete any of the missing files as long as it doesn't match your package to the older version by CFBundleID or package name. This email sent to ryanc(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0