January 2006 - Installer-dev

Re: Is it possible to display more than one License file or Readme?
by Bill Coderre 31 Jan '06

31 Jan '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Is it possible to display more than one license or readme during a distribution installation? Not without coding around the Installer's current behavior. _______________________________________________ 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 Jan 31, 2006, at 11:36 AM, Kevin Hoyt wrote: For example, if the license for one of the sub-packages is different from the rest, could it be displayed in addition to the main one for the distribution? Same question for a reame file... You COULD do this by running an application or writing an Installer plugin (Tiger-only), but if you think about it for a minute, it's a yucky user experience. (I suppose it's also possible to chain several installers together, such that when the user finishes one installer, the next is automatically launched.) For iLife, Apple made an "all-encompassing" License agreement that covered all the details of the included apps, same for the Welcome and ReadMe. This email sent to site_archiver(a)lists.apple.com

1 0

Is it possible to display more than one License file or Readme?
by Kevin Hoyt 31 Jan '06

31 Jan '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi all, Is it possible to display more than one license or readme during a distribution installation? For example, if the license for one of the sub-packages is different from the rest, could it be displayed in addition to the main one for the distribution? Same question for a reame file... Kevin Hoyt _______________________________________________ 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

how does 10.4.4's installer determine pkg version?
by Julian Devlin 25 Jan '06

25 Jan '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks -Julian _______________________________________________ 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.… I am trying to sort through the various Version properties which can appear in a plist, and determine how to use each one. We use four digits (e.g. 1.2.3.4) for our software versioning, and a change in the final digit implies a new release. In the past, we have put the full version, 1.2.3.4, in the CFBundleShortVersionString. We did this both for our .apps, .pkgs, and .mpkg. Starting with the Tiger version of Package Maker, we started getting a warning that CFBundleShortVersionString should only contain three numbers. This agrees with an Apple document which I found: http://developer.apple.com/documentation/MacOSX/Conceptual/ BPRuntimeConfig/Articles/PListKeys.html#//apple_ref/doc/uid/20001431 -111349 I also found this document with a section called "How Installer Computes a Version": http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/Concepts/sd_pkg_version_info.html#//apple_ref/doc/ uid/20001942-1016661-CEGBFEAA This document suggests that we should set CFBundleShortVersionString to 1.2.3 and SourceVersion to 4, and then the installer will see the version as 1.2.3.4. So this is what we did. Tiger Package Maker stopped showing an error, and the mpkg/pkgs worked fine in 10.3, and earlier versions of 10.4. As of 10.4.4 however, the behavior seems to have changed. If an earlier version with CFBundleShortVersionString of 1.2.3.4 is already installed and we try to install a new version with CFBundleShortVersionString 1.2.3 and SourceVersion 5, this is seen as a downgrade. Likewise, if an earlier version with CFBundleShortVersionString of 1.2.3 and SourceVersion 4 is already installed and we try to install a new version with CFBundleShortVersionString 1.2.3 and SourceVersion 5, this isn't seen as a downgrade or an upgrade - by default the subpackages in our mpkg are not selected (apparently since installer sees the two versions is equal). So, my conclusion is that the installer that is used with 10.4.4 ONLY looks at CFBundleShortVersionString, so we will have to revert to using our full version in that property, despite the warning of the package maker. Could anyone offer any advice on why 10.4.4 installer has changed like this, and whether there is any better solution? This email sent to site_archiver(a)lists.apple.com

1 0

Re: The package could not be created because of the following error (no errors!)
by Jonathan Wight 23 Jan '06

23 Jan '06

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com On Jan 23, 2006, at 3:22 PM, Peter Bierman wrote: The package could not be created because of the following errors: No root specified for archive. Jon. _______________________________________________ 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.… You can also try executing packagemaker with the full path: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker Both of these solutions work around bugs that we're investigating. [schwa@umbriel] Packaging$ /Developer/Applications/Utilities/ PackageMaker.app/Contents/MacOS/PackageMaker -build -proj Python\ Metadata\ Importer.pmproj -v Well at least now we have error messages... The project should have a root though. Like I said it builds fine from the GUI. This email sent to site_archiver(a)lists.apple.com

1 0

Re: The package could not be created because of the following error (no errors!)
by Peter Bierman 23 Jan '06

23 Jan '06

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com If I use the following command: "packagemaker -build -proj Python\ Metadata\ Import.pmproj -v -p Test.pkg" I get this error: "The package could not be created because of the following errors:" Try adding a '-v' to the packagemaker command line. You can also try executing packagemaker with the full path: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker Both of these solutions work around bugs that we're investigating. -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/site_archiver%40lists.… At 5:44 PM -0500 1/21/06, Jonathan Wight wrote: Unfortunately there are NO following errors and nothing is output. This email sent to site_archiver(a)lists.apple.com

1 0

Re: The package could not be created because of the following error (no errors!)
by Peter Bierman 23 Jan '06

23 Jan '06

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com -pmb Jon. On Jan 22, 2006, at 2:21 PM, Kevin Hoyt wrote: I have a bug opened for this... 4397457 It's currently in 'Duplicate' state. I hope it gets fixed soon so I can fully automate the package process... On Jan 21, 2006, at 2:44 PM, Jonathan Wight wrote: If I use the following command: "packagemaker -build -proj Python\ Metadata\ Import.pmproj -v -p Test.pkg" I get this error: "The package could not be created because of the following errors:" This on Mac OS X 10.4.4 (PPC) with Xcode 2.2.1 _______________________________________________ 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/bierman%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.… Heh. I know it seems that way, but we don't just forget about bugs even if they're marked as a duplicate. In fact, bugs that have lots of duplicates reported are more conspicuous. At 2:26 PM -0500 1/22/06, Jonathan Wight wrote: I've got it as rdar://4417540 - currently open but I'm guessing on Monday it'll get marked as duplicate and then forgotten about. I have a Spotlight plug-in that i am trying to release an Intel version of. Because the plugin needs to be installed in /Library/Spotlight I have created a Package Maker project for it. My build script uses /Developer/Tools/packagemaker to produce the installer from the project Unfortunately there are NO following errors and nothing is output. The project builds and validates correctly if I use the Project Maker GUI to build the project. The code is available from "http://svn.toxicsoftware.com/svn/toxic_public/branches/Python%20Metadata%20…" and running "Release.sh" should build and try to package the code. Jon. This email sent to bierman(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: The package could not be created because of the following error (no errors!)
by Jonathan Wight 22 Jan '06

22 Jan '06

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Jon. On Jan 22, 2006, at 2:21 PM, Kevin Hoyt wrote: I have a bug opened for this... 4397457 It's currently in 'Duplicate' state. On Jan 21, 2006, at 2:44 PM, Jonathan Wight wrote: If I use the following command: I get this error: "The package could not be created because of the following errors:" This on Mac OS X 10.4.4 (PPC) with Xcode 2.2.1 _______________________________________________ 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.… I've got it as rdar://4417540 - currently open but I'm guessing on Monday it'll get marked as duplicate and then forgotten about. I hope it gets fixed soon so I can fully automate the package process... I have a Spotlight plug-in that i am trying to release an Intel version of. Because the plugin needs to be installed in /Library/ Spotlight I have created a Package Maker project for it. My build script uses /Developer/Tools/packagemaker to produce the installer from the project "packagemaker -build -proj Python\ Metadata\ Import.pmproj -v -p Test.pkg" Unfortunately there are NO following errors and nothing is output. The project builds and validates correctly if I use the Project Maker GUI to build the project. The code is available from "http://svn.toxicsoftware.com/svn/ toxic_public/branches/Python%20Metadata%20Importer%20Stable/" and running "Release.sh" should build and try to package the code. Jon. This email sent to site_archiver(a)lists.apple.com

1 0

The package could not be created because of the following error (no errors!)
by Jonathan Wight 21 Jan '06

21 Jan '06

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com If I use the following command: I get this error: "The package could not be created because of the following errors:" This on Mac OS X 10.4.4 (PPC) with Xcode 2.2.1 Jon. _______________________________________________ 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.… I have a Spotlight plug-in that i am trying to release an Intel version of. Because the plugin needs to be installed in /Library/ Spotlight I have created a Package Maker project for it. My build script uses /Developer/Tools/packagemaker to produce the installer from the project "packagemaker -build -proj Python\ Metadata\ Import.pmproj -v -p Test.pkg" Unfortunately there are NO following errors and nothing is output. The project builds and validates correctly if I use the Project Maker GUI to build the project. The code is available from "http://svn.toxicsoftware.com/svn/ toxic_public/branches/Python%20Metadata%20Importer%20Stable/" and running "Release.sh" should build and try to package the code. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Gestalt check for OS version is failing on Intel Macs
by Christopher Ryan 20 Jan '06

20 Jan '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com <key>IFRequirementDicts</key> <array> <dict> <key>SpecArgument</key> <string>/System/Library/CoreServices/SystemVersion.plist</string> <key>SpecProperty</key> <string>ProductVersion</string> <key>SpecType</key> <string>plist</string> <key>TestObject</key> <string>10.3.8</string> <key>TestOperator</key> <string>ge</string> <key>LabelKey</key> <string>OS Version</string> <key>Level</key> <string>requires</string> <key>MessageKey</key> <string>messagekey0</string> <key>TitleKey</key> <string>titlekey0</string> </dict> </array> Chris Hi Mark, - Luke On Jan 20, 2006, at 9:15 AM, Mark Krenek wrote: <key>IFRequirementDicts</key> <array> <dict> <key>LabelKey</key> <string>OS Version</string> <key>Level</key> <string>requires</string> <key>MessageKey</key> <string>messagekey0</string> <key>SpecArgument</key> <string>sysv</string> <key>SpecType</key> <string>gestalt</string> <key>TestObject</key> <string>4152</string> <key>TestOperator</key> <string>>=</string> <key>TitleKey</key> <string>titlekey0</string> </dict> </array> _______________________________________________ _______________________________________________ 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 workaround, assuming you haven't shipped your product yet is to change the requirement to: This is an issue we are aware of. We have a fix for it and are working to have that fix available to customers as soon as possible. I'm using a gestalt requirement key in my installer to check for 10.3.8 or later. This has worked fine until 10.4.4 on Intel Macs. On these new Intel Macs, the Installer fails the Gestalt check. 10.4.4 on PPC Macs work just fine. Anyone have any ideas? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Gestalt check for OS version is failing on Intel Macs
by Luke Bellandi 20 Jan '06

20 Jan '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi Mark, - Luke On Jan 20, 2006, at 9:15 AM, Mark Krenek wrote: <key>IFRequirementDicts</key> <array> <dict> <key>LabelKey</key> <string>OS Version</string> <key>Level</key> <string>requires</string> <key>MessageKey</key> <string>messagekey0</string> <key>SpecArgument</key> <string>sysv</string> <key>SpecType</key> <string>gestalt</string> <key>TestObject</key> <string>4152</string> <key>TestOperator</key> <string>>=</string> <key>TitleKey</key> <string>titlekey0</string> </dict> </array> _______________________________________________ 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/luke%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.… This is an issue we are aware of. We have a fix for it and are working to have that fix available to customers as soon as possible. I'm using a gestalt requirement key in my installer to check for 10.3.8 or later. This has worked fine until 10.4.4 on Intel Macs. On these new Intel Macs, the Installer fails the Gestalt check. 10.4.4 on PPC Macs work just fine. Anyone have any ideas? This email sent to luke(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0