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

Re: PackageMaker 3.0.1 and requirement script
by Steven Meyer 06 Mar '08

06 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=p7B9B2OqBlJkvxrYME589/XvC3w301J3V1jzje5eR1wKe8uk95fnCejKb6hAso/3; h=Received:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Content-Transfer-Encoding:Cc:From:Subject:Date:To:X-Mailer:X-ELNK-Trace:X-Originating-IP; Finally some other issues On Mar 4, 2008, at 4:55 PM, Stéphane Sudre wrote: On Mar 4, 2008, at 1:52 PM, Steven Meyer wrote: _______________________________________________ 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 switched from PackageMaker 3 to PackageMaker 2 and resolved my problems. For the sake of anyone using PackageMaker 3, I thought I would make some comments. Good things Distributions can be created in one project which generates the individual packages as well as the distribution. Packagemaker has post install automator actions. Bad things The new PackageMaker uses a new pmdoc format. Upgrading requires user input. Things work differently with scripts, and examples are sparse or non-existent. I could not find a way to edit the built packages. The Flat Package Editor was not working on them. Then you're creating a FLAT package that is compatible with Mac OS X 10.5 or later. You can edit it later using the Flat Package Editor but this is not really easy. The packagemaker project allows you to set compatibility. My project was set for 10.4 and later. The Flat Package Editor was not working. PackageMaker now has a "Raw Edit Mode" that does some of the same things. I was able to use "Raw Edit Mode" to insert an Installer plugin. Manually or through a shell script (which would mean, you may need to build your package/distribution script through the PackageMaker command line). I have only extensively used the latest PackageMaker. The packages produced can not be viewed in the finder with "Show Package Contents". Then you're creating a FLAT package that is compatible with Mac OS X 10.5 or later. You can edit it later using the Flat Package Editor but this is not really easy. This email sent to site_archiver(a)lists.apple.com

1 0

RE: Drive selection in 10.5
by John Williams 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Ach/FXLSnA8D1Im6RfOcYoa+lXsxVgAAG/ag Thread-topic: Drive selection in 10.5 Well, at least thanks for the chuckle, Stéphane! I find it amusing that Apple is now recommending the use of 'managed installations' but their tools are woefully inadequate for the job. -----Original Message----- From: Stéphane Sudre [mailto:iceberg-dev@orange.fr] Sent: Wednesday, March 05, 2008 6:06 PM To: John Williams Cc: installer-dev(a)lists.apple.com Subject: Re: Drive selection in 10.5 On Mar 5, 2008, at 4:49 PM, John Williams wrote: > Hi, > > I have a distribution created with PackageMaker 2.1.1 that is working > oddly on 10.5. > > Here's the scenario (shortened a bit) > - Restart mac (to ensure a clean slate) > - Run installer > - Click through license agreement > - Get volume selection page > - Pick a volume and continue > - Get custom install page > - Click continue > - Get ready to install page > - Quit installer > > - Run installer again (without restarting) > - Click through license agreement > - Get custom install page (no volume selection page) > - Click Continue > - Get ready to install page, but this time there's a Change Install > Location button > -- Clicking this button takes you back to the License Agreement page > -- You can never get to the volume selection page > > The installer is set to always show a Custom install since we have > various plug-ins, system startup files, standalone apps, etc that can > be installed. > I'm assuming OS X is caching the location requirements somewhere but I > haven't been able to figure a way around this. > > Any ideas? IMHO, It's a bug. I'm not able to find the Radar number for it but I'm pretty sure I reported it a long time ago (1 year ago). It could be 5007444 which was a duplicate of 4594713. This problem is visible with the Xcode installer for instance. Basically, what you will see depends on whether Punxsutawney Phil sees its shadow or Bill Murray. Which is not a good thing for end- users (and Phil). _______________________________________________ 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: Drive selection in 10.5
by Stéphane Sudre 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2008, at 4:49 PM, John Williams wrote: Hi, Here's the scenario (shortened a bit) - Restart mac (to ensure a clean slate) - Run installer - Click through license agreement - Get volume selection page - Pick a volume and continue - Get custom install page - Click continue - Get ready to install page - Quit installer This problem is visible with the Xcode installer for instance. _______________________________________________ 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 distribution created with PackageMaker 2.1.1 that is working oddly on 10.5. - Run installer again (without restarting) - Click through license agreement - Get custom install page (no volume selection page) - Click Continue - Get ready to install page, but this time there's a Change Install Location button -- Clicking this button takes you back to the License Agreement page -- You can never get to the volume selection page The installer is set to always show a Custom install since we have various plug-ins, system startup files, standalone apps, etc that can be installed. I'm assuming OS X is caching the location requirements somewhere but I haven't been able to figure a way around this. Any ideas? IMHO, It's a bug. I'm not able to find the Radar number for it but I'm pretty sure I reported it a long time ago (1 year ago). It could be 5007444 which was a duplicate of 4594713. Basically, what you will see depends on whether Punxsutawney Phil sees its shadow or Bill Murray. Which is not a good thing for end- users (and Phil). This email sent to site_archiver(a)lists.apple.com

1 0

AuthorizationExecuteWithPrivileges error -60008
by Fritz Anderson 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com — F _______________________________________________ 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 issue was resolved on the Apple-cdsa list, but I want to reflect the solution here to increase its visibility to searches, and in case it may be useful to other subscribers. An application I run from my mpkg package launches a handful of tools that must execute with elevated privileges. I did this with AuthorizationExecuteWithPrivileges. The tools were not executed. AuthorizationExecuteWithPrivileges instead returned with the error code -60008. Error -60008 is errAuthorizationInternal, "An unrecognized internal error occurred." Internal errors are never good news, and I asked Apple-cdsa about it in some despair. Google searches turned up the error only in other, often end-user, contexts. The response was this: AuthorizationExecuteWithPrivileges requires that the environment variable TMPDIR be set to a "valid" directory, presumably meaning both existing and read/writable. Installer.app creates such a directory, and sets TMPDIR, but by the time my application runs, the directory is deleted. AuthorizationExecuteWithPrivileges can't proceed, and reports -60008 (errAuthorizationInternal). This isn't documented anywhere I can find, and my correspondent's assertion that it is a "known issue" begs the question of who knows it. I am annoyed. Documentation bug filed. The workaround is to create a directory for the purpose in /private/ tmp, and set TMPDIR to its path, before launching the helper application. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Questions on localised strings
by Stéphane Sudre 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2008, at 4:20 AM, Jose R.C. Cruz wrote: - localizedString(key) - localizedStringWithFormat(key, arg1, arg2,..) - localizedStandardString(key) - localizedStandardStringWithFormat(key, arg1, arg2,..) GENERIC_FAIL_LANG GENERIC_FAIL_VOLUME GENERIC_FAIL_NEWER _______________________________________________ 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 couple of questions that I hope some you could help. The System object has the following calls: For the first two calls, I assume the strings must be in the file Resources/Localizable.strings, am I correct? But what about those standard strings? Are these strings that came with Installer.app? Or are they located somewhere else in CoreServices? >From what I can see, localizedStandardString can accept localization keys from the Distribution.strings file located in /System/Library/ PrivateFrameworks/Install.framework/Versions/A/Resources/. At this time, this is the only .strings file I have been able to use from Installer.app resources, Installer.app plugins and Install.framework But there might be other possible keys because one of the Printer Drivers updates from http://swcdn.apple.com/ is using the following keys: I agree the description for localizedStandardString and localizedStandardStringWithFormat is not describing anything. Think about reporting this lack of information through the "Did this document help you?" report mechanism at the bottom of the documentation. This email sent to site_archiver(a)lists.apple.com

1 0

Drive selection in 10.5
by John Williams 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Thread-index: Ach+2IhYSZTbR4n8SG6eD7f3eopdpg== Thread-topic: Drive selection in 10.5 _______________________________________________ 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

Questions on localised strings
by Jose R.C. Cruz 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; bh=B1973MncjJ4E+tKrd/GC0T1SoU5IPQIM9FRKPzQD8XU=; b=oM4Y6+LmAti+o43i4FgZhFNXmd/xDNM7Kxvbm7+cGzg0jM6HtNKNYq1qqciKwVtCpbYsi7KjTPKNBVqObr5R36iZrcIoXiyo2h+cxNm1I/2qdXTL/fVsKmsxiXNadO6WjOumZtbKFP0cG6vFG/EhMIx80805AMzgJL8X61p9D2g= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; b=S1O6crwb7sIrDd2nFDDe3WB+oQGt+7cKuUmWNjoTBPEtbSseva6m/M8TNExZfYOYtjm7rx1NqB7vzx2p2R2O/RpnCcUBD9F+S579zgDJKpWhNs26IrllBjiYIOaUNLf4m1IXCRCax2KGzdxv2ae+EkM8KtqVEqVTh4nzeqPjeGE= - localizedString(key) - localizedStringWithFormat(key, arg1, arg2,..) - localizedStandardString(key) - localizedStandardStringWithFormat(key, arg1, arg2,..) I appreciate any insight you can give. ----- Jose R.C. Cruz anarakisware(a)gmail.com 1.778.882.1315 _______________________________________________ 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 couple of questions that I hope some you could help. The System object has the following calls: For the first two calls, I assume the strings must be in the file Resources/Localizable.strings, am I correct? But what about those standard strings? Are these strings that came with Installer.app? Or are they located somewhere else in CoreServices? Also, is there an easy way to add the file Localizable.strings to the install package as it is being built? I find it cumbersome to have to insert said file manually after each build. This email sent to site_archiver(a)lists.apple.com

1 0

Re: setting permissions of installed items from command line
by Stéphane Sudre 05 Mar '08

05 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2008, at 12:37 AM, Philip Wasson wrote: - build your Xcode project with the Xcode command line tool run as root or - create a setuid tool that changes the permissions _______________________________________________ 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 would like to be able to build installer packages from a shell script called from a Run Script build phase in my Xcode project. However, apparently I'm supposed to set the ownership of applications to be installed into /Applications to root and admin, right? Xcode won't be running as root, so a script it calls can't chown to root. Is there some tool or technique to allow this? I saw some similar questions on this list and also the unix-porting list, but no answers. Any ideas? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Debugging Installer Plugins
by Stéphane Sudre 04 Mar '08

04 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 3, 2008, at 8:45 PM, Robert Kukuchka wrote: 1. Open your Installer Plugin Xcode project 3. In Xcode, still with your Installer Plugin project: i) Choose Project > New Custom Executable... ii) Click Choose... iv) Click Finish v) Set your breakpoints vi) Choose Debug > Debug Executable 4. Debug _______________________________________________ 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.… How can I set up a Custom Executable to properly Debug an Installer Plugin from within XCode 3.0? With most bundles it's a fairly straight forward process, but I'm missing something in setting this up. Any helpers out there? Here's how you can do it in Xcode 2.3 (I don't think it would be different with Xocde 3.0) (*) 2. Create the debug version of your plugin and add the plugin to the appropriate package/metapackage. iii) Select Installer.app (in /Applications/Utilities on Mac OS X < 10.5 and in /System/Library/CoreServices/ on Mac OS X 10.5) (*) Adapted from the post on Unsanity weblog (http://unsanity.org/ archives/000391.php) This email sent to site_archiver(a)lists.apple.com

1 0

setting permissions of installed items from command line
by Philip Wasson 04 Mar '08

04 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com TIA ---------------------------------------------------------------------- Philip D. Wasson pwasson at maned dot com MEI Software Engineer _______________________________________________ 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 would like to be able to build installer packages from a shell script called from a Run Script build phase in my Xcode project. However, apparently I'm supposed to set the ownership of applications to be installed into /Applications to root and admin, right? Xcode won't be running as root, so a script it calls can't chown to root. Is there some tool or technique to allow this? I saw some similar questions on this list and also the unix-porting list, but no answers. Any ideas? This email sent to site_archiver(a)lists.apple.com

1 0