February 2010 - Installer-dev

Bugs, Certificates, PackageMaker and Installer
by Iceberg-Dev 18 Feb '10

18 Feb '10

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:mime-version :content-transfer-encoding:message-id:content-type:to:from:subject :date:x-mailer; bh=3grqZt5nBgMwxRVo2O/8wZCkW9sum6u5Z/yJnNZG3RE=; b=HcyO/fnRRaZzrI/q8HhzVYWS3ant0/+9E656PMYu8p0zSoltbiznBqLUXiCuAFLByE k5ULYS/sDPtHvVk52Sf21XG1s76y0RxKbds38mGVSmZYPx7yWu+jKRYc0z+V0pPIQR+v ZYlRomTRJa5h8gVVinpFlGbyxfc91nlzvfafk= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-transfer-encoding:message-id:content-type:to :from:subject:date:x-mailer; b=itdYPx7Q8roKbyxbhY0fiELdz6ZWWm7QkPU/ptoZ1TI/1dvbMjH0AYNA6wvRrUR9O+ SOffF0Mel4I5fnu2/agSe1X2agFlcQDU6w3abXBAxK8zrAeYkA+p5paKQZwhVBME7i0I IBSq3UFEBiX6MbWrGhdDvZ3SEKGBOUTG+BMxg= It will set the relative path to file:./../MyPackage.pkg. All of this with the latest OS X version and the latest Dev Tools. _______________________________________________ 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.… While playing with PackageMaker to try to figure out where the hash- sha256 value was coming from in a distribution script, I think I bumped into numerous bugs in PackageMaker. Bug #1: If you create a flat distribution with one of the packages being at the same level of the distribution, the relative path of the package is incorrect in the Distribution. This is correct for a bundle distribution. Not for a flat distribution apparently. I'm not the one saying that. Installer.app is. Bug #2: If you put the package one level higher, Installer.app will then complain that the hash-sha256 key-value is missing for the package. Bug #3: If you try to sign this distribution, the related package will be signed too (which is OK AFAIK). But Installer.app will fail saying the package can not be trusted or something like that. Bug #4: The error message for Bug #3 is totally unclear and put the blame on the author of the package while it's not the guy's fault but either PackageMaker or Installer.app fault. Bug #5: If you don't sign the distribution, the installation will fail with Installer.app complaining that there is no software to install. I will definitely file numerous bug reports in Radar so that this can be tracked. This email sent to site_archiver(a)lists.apple.com

1 0

Re: add-on installers
by Iceberg-Dev 18 Feb '10

18 Feb '10

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:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=flPK3GNbF0O1yZYpRHA9iPxHpcHM9dqq48yMYCk2bKY=; b=vc8Wpy8ZULSJqZdz3x8Q65EJxP2BeWpnBtb/EVB2Fbb72hl5qralaJhrlTv4XMeLok UW61W7ULGXbOOQxJjszmE/9zm72EoP5ijU+dexLBfpM7cTfKzXzK3MIQMBrwR5EbdHrq t65/cUzr04b2tRRU9m9B7AZ38Ic9P7VbumX9Q= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=L6Xvjg+MKAhWz2y0pJMAHmexS16x1mClx76KPe65BSEeFA2DVwHBu5GCqObkQvhY2R RRxgnUeTRXiXu56lPZeq8lBGht/MpWhxOjqRflKc9XFbov2jy9azg1+kTbPDCUCgEOo6 QVZog1888EdQtsctoc24LIcUOkoTJ/cd/hJxE= On Feb 18, 2010, at 4:48 PM, sakshi wrote: Hi, Use Search Locators. You don't need (an don't want) to use a patch. _______________________________________________ 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 need to create a Primary installer which installs the main application and supplementary installers which the users could opt to install later. The supplementary installer would have to find where the primary installed the main application and then add files to the application's bundle. Are there are recommendations/known approaches on creating such a supplementary installer? The crude approach would be to install to /tmp/ and then use postinstall steps to figure out which disk the application was actually installed on and then move the files there. I am sure I can do better than this :). I have seen the patch root option in the PackageMaker UI and it made me wonder if I could somehow use it. Would anyone have links to any documentation on how patching works with PackageMaker? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Different "Quit App" behavior between PackageMaker.app and cmd line
by Iceberg-Dev 18 Feb '10

18 Feb '10

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:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=pwc1hoN70LxC0UizYcQtyh+ume4YGlJYfo1lBI3vyzY=; b=UIcvmPQNV/OY3s2sdwReNvdeFXATuYlHYIJFxDxF6eh8JgUyY4hh8d8nP11EqGPg/x 4GUg7kPpf5mA2ayqhwvdP5XVA2ZKqGCA2m1zVCxljbq8KxATBUQQ0GL5rXHMEC2ms4Hv T5eBjjaQmkzZaXsVaCKnWP4fo4/EDaryiTrpU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=CSKm3Bz/1y2baCe6U3mAtgNwXyRiOqoRRFx6qC3mY+8IBM29EXFVV0cN0xkCuEMKCe sh+Jlh9MUgQl56MUJjj2HcsPJsWzC35y5DloxGSIp+1uuG/QJO+c+esHm9QSxzVvwRi6 zFLcLhHDmPzzQkG7lP/EnFyQzyn+P9VksQu4o= On Feb 18, 2010, at 3:08 AM, Matt Ronge wrote: Hi, _______________________________________________ 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'm having a strange problem with PackageMaker. My installer makes sure an app (Mail in this case) is not running, and if it does, quits it. I used the Actions tab of PackageMaker to build this action. It is a "Get App" attached to a "Quit App". Now here is where it gets strange... If build the installer with PackageMaker.app, it works great. If Mail is running it quits it and proceeds with with installation. HOWEVER if I build the installer with the command line tool /Developer/usr/bin/ packagemaker, it installs but it WON'T quit Mail if it's running. It just leaves it running and does the install anyway. Why the difference in behavior? I use this to build on the cmd line: "/Developer/usr/bin/packagemaker -d installer/ myinstaller.pmdoc -o build/MyInstaller.pkg" Have you checked if there's any difference between the package you get when you use the UI and the one you get when you use the command line? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Snow Leopard GUI order
by Iceberg-Dev 18 Feb '10

18 Feb '10

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:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=OGwKKwZ5o1jtTVXS6ffONTRo/UOLElCNOlYhf2a05h0=; b=hsz2QgVh2q2sTgVt5NlAGG9Z47x3TeMJYNptT3/Mq7bj2Y4k8EToD4XyRwgydUlkH8 zWW9/oHJxsfc5mhJMYcvTmIMP4RVJZdAqV1aCT5ml5hAMCQEURJcYettvxCpDKmcI4p9 6uYOioRQbXnswNpfAqAH3WndCcnquHnqnz4Co= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=VO/oAqH1XNi+2TwDsNdHxv2wM5aX9vujRgUtcrd3Vz1ZoDSFdpMEzSuj9cQI5rUwi8 9GvXqAm/8O1kvM+gH5vkSAY/oZby+B+tZRTSZylLK/OQt/en0r4o/boNWogdefIlMq4Q zsanIYSYG61KTNElWsLkuuqL+E7CcKZOenp/A= On Feb 18, 2010, at 2:51 AM, Hafen, Keith wrote: Introduction ReadMe Target License Registration.Bundle Package Selection Install Introduction Destination Select License Server Installation Type Installation Summary And as you step through the UI they come up in that order. License should be before Target. _______________________________________________ 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 have a Install Package that works fine on Leopard. It installs a license server, so we have a custom plug-in that allows the user to browse for a license file. In the plugin directory is an InstallerSections.plist that has the UI sequences listed: On Leopard the UI comes up and on the left hand side lists the screens in order: The order listed for the items in the InstallerSections.plist is incorrect. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Installer-dev Digest, Vol 66, Issue 16
by Don Montalvo 18 Feb '10

18 Feb '10

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:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=s2sciRuz3DrmSJOeU9UHoCnd/fW2s6gmfuf9rjZVh14=; b=jbA4R5CBtn7TdYmPD3nzd3NetXoPk5BvxUXLzC9BOK35alFfgTfOVnRydkUZymekZ9 eUNk6SG9v3nrYCjmML60hh7SFolpufYcZi1z9p8wwet84QMpQnXiJOr2EGlDbBkuLczx p2V0aMbTFjiesQ3yJ4COx09yMXiXHZD20/5RY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=gwLJmsUuuhvxRx/mgNRfuYuhANAoLGZKhmLYmeCb0KzNLtg8NGnx4mZB9o85JuVugl qNtZuJjE18CMgQ1gbPODGT8NGLW4qQBrLQ2otScwXYJJEHl2Pn7U0pTUTrJSXC8G3Q5k ZgpTEJfJ3LypXEBpWF+SMk9v5JA0XaLaGseAk= Sudre mentioned conversions may not be possible so we're recreating the package from scratch. Using Packages, we added the one file that gets installed (/usr/sbin/jamf) and we renamed the "postflight" script to the required "postinstall" name. Checked to make sure the permissions are right, will test tomorrow. If this works, we're going to ask JAMF to add an option to save the Quick Add installer as a flat pkg for email distribution. :) Thanks, Don On Feb 17, 2010, at 12:52 PM, installer-dev-request(a)lists.apple.com wrote: > Date: Wed, 17 Feb 2010 15:39:43 +0530 > From: Karthikeyan Marappan <karthikeyan.mac(a)gmail.com> > Subject: Re: Convert a pkg installer to a flat package installer? > To: installer-dev(a)lists.apple.com > Message-ID: <2366073E-60AB-4FC5-8317-172DEE2DF484(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > I tried converting normal package to flat package on PackageMaker, but it fails. Let me explain the followed procedure. > > 1. Opened the .pkg with PackageMaker. > 2. Change the minimum target to "Mac OS X v10.5 Leopard" in "Install Properties" of Project Menu. When I tried building it showed Permission error, so Applied recommended permissions. > 3. Again when tried building the Package, it shows "Could not unarchive the package payload". (Even If i open the same .pkg with packagemaker and tried building the package without any modifications, It shows same error). > > Any other options to convert it to Flat package or any other modifications to be done? > > Regards, > Karthikeyan M > > On Feb 13, 2010, at 7:17 AM, Bob Sellon wrote: > >> Actually, the other way round. Set it for 10.5 (for the PackageMaker). >> >> On Feb 12, 2010, at 8:42 PM, Bob Sellon wrote: >> >>> I only recently discovered the Project/Raw Editing Mode so I haven't had a chance to check this but if you set the "Minimum Target" under Project/Install Properties.. to v10.4, it is supposed to switch to the non-flat format. >>> >>> >>> On Feb 12, 2010, at 8:31 PM, Don Montalvo wrote: >>> >>>> On Feb 12, 2010, at 7:29 PM, Don Montalvo wrote: >>>> >>>>> Is it possible to convert a standard pkg installer > flat pkg installer? >>>>> >>>>> I'm looking through Apple's (and of course Sudre's) documentation but don't see any way to do this. >>>>> >>>>> Thanks, >>>>> Don >>>> >>>> ...a follow up question. If conversion is not possible, is it feasible to create a new project, import our existing pkg installer, then save as a flat pkg? >>>> >>>> PS, Sudre, please point me to your PayPal page.... :):):) >>>> >>>> Thanks, >>>> Don _______________________________________________ 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

prevent packaging of resource forks
by David Schara 18 Feb '10

18 Feb '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Importance: normal Sensitivity: Normal _______________________________________________ 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

add-on installers
by sakshi 18 Feb '10

18 Feb '10

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:mime-version:received:date:message-id:subject :from:to:content-type; bh=/oPmm1RO+aJzaRzFuI4ABIWWwcKwnrG+r+wqhKvgAs8=; b=BB5jGZSCOYFmsozX02A5gqXWK9wRVYz0yecUamtPcU0k2fYgtJ8o3cK16ig0J/k7Vj LOuqTZRQQXP8Ssupmad6BebJkqoIy/TvrXlwGxPZHPAjQJIShQfnjz4PU6KDr6QQ5qbT ZTbtU7HHNud67+cIqiT05gq1JwEBVB1kz0goE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GPePAACEmzPvPsHNSc/DD0AOsoZflah5DnxL1RosfidlPORkHnKSc7WkjRNq6ldz1X xVO/nPkcrk5UP1GGi7udkFvSUxgNtVlZi2YzpQ4Vge2KiL5Fu1DhDihDNBtjP4he7EwX qfHYy4qMs7l08RMFsG9waFV/HvpGUqVrNeXBM= _______________________________________________ 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

Different "Quit App" behavior between PackageMaker.app and cmd line
by Matt Ronge 18 Feb '10

18 Feb '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, I'm having a strange problem with PackageMaker. My installer makes sure an app (Mail in this case) is not running, and if it does, quits it. I used the Actions tab of PackageMaker to build this action. It is a "Get App" attached to a "Quit App". Now here is where it gets strange... If build the installer with PackageMaker.app, it works great. If Mail is running it quits it and proceeds with with installation. HOWEVER if I build the installer with the command line tool /Developer/usr/bin/packagemaker, it installs but it WON'T quit Mail if it's running. It just leaves it running and does the install anyway. Why the difference in behavior? I use this to build on the cmd line: "/Developer/usr/bin/packagemaker -d installer/myinstaller.pmdoc -o build/MyInstaller.pkg" Thanks for any help, -- Matt Ronge Founder Central Atomics Makers of Rocketbox! http://www.getrocketbox.com mronge(a)centralatomics.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 email sent to site_archiver(a)lists.apple.com

1 0

Snow Leopard GUI order
by Hafen, Keith 18 Feb '10

18 Feb '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcqwPONV9OtXtGvfSkmEtsh2P6T4bg== Thread-topic: Snow Leopard GUI order _______________________________________________ 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: "Installer could not install the software"
by Andrew Peckover 17 Feb '10

17 Feb '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks for the reply. Andrew On Feb 17, 2010, at 1:23 PM, Andrew Peckover wrote: hi- I think we did during alpha testing. (your milage may vary) thanks!- -lance _______________________________________________ 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 installer was made on Leopard with PM version 3.0.3, and is being installed on Snow Leopard. We have other customers using the same installer on Snow Leopard, and they aren't experiencing this problem. So it leads me to believe there is something specific about this customer's system that's causing the problem ? Or maybe it's a new issue with the most recent Mac's and this customer is just the first to report it.. ----- Original Message ----- From: "lbland" <lbland(a)vvi.com> To: "Andrew Peckover" <apeckover(a)pgmusic.com> Sent: Wednesday, February 17, 2010 10:45 AM Subject: Re: "Installer could not install the software" "Installation Failed. Installer could not install the software. No software found to install" Has anyone seen this error before? If you have a Leopard Package Maker project and then use the Snow Leopard Package Maker on the same document to make the installer package then you can get the error you see on Snow Leopard. The solution we found was to delete the Package Maker document and start from scratch for a Snow Leopard only install using only the Snow Leopard Package Maker. You may also just use Leopard to make your installer and that worked for us on Snow Leopard as well. This email sent to site_archiver(a)lists.apple.com

1 0