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

how to make an applescript fail
by spondita Madhuri Neog 31 Mar '10

31 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcrQoaaZmflpTi89RLedxxUbe8nJmQ== Thread-topic: how to make an applescript fail _______________________________________________ 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: Install/upgrade compatibility for package version numbers derived from VCS data
by Iceberg-Dev 30 Mar '10

30 Mar '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=Yk1MN/s5b8+KOVKe7PnUj0OBC3YAEiNl8ue5XuZL4o8=; b=Exjxbv3nnJK6txP5I0sk8ZYQX/UZbe4rHJgMoBpq7y3GHS2QAQIvdyWkN51VAtxmjV /rWhVnrIvfwaI2AO7Q9M+EC9YD8IqLQTeicZziuRBTIvJIj4HFqFfY2J9tRbCNgv0zRx dhIiitWTVhLfEG+3StobIS7Y6ZEmMmopwDhg0= 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=UR4FIWy1RKlgIglAql9gUzAAta7IaB7Y1+WhNr9Krupr35hXqZcQnYQ0Lydnzq5Txd jwxnTwU9uMdB0UQ0ECbdc4xsSFgInXALRBCgrvdE2MsIWkJwJ8ZQF58dIobrxDKHrZXg 6ATD26aTHkAV/nQEe/etWTaRjRjyGfXHXyn5c= On Mar 30, 2010, at 4:27 PM, Jeremy Reichman wrote: So it requires testing it. _______________________________________________ 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 interested in the idea of using semantic versioning for packages I'm deploying. These packages start out from Mercurial repositories, so I can derive the version number from the semver tags ('v1.0.0') and other data from the repository to construct Really Specific Version Numbers during my automated package building process. In the following case, I use the tag plus the distance from the latest tag and the short hash of the current revision. $ hg log -r. --template '{latesttag}+{latesttagdistance}-{node| short}\n' | sed -e 's/^v//' 1.0.0+1-df34ebfc12c9 The version number used in some Apple packages is bigger than xx.xx.xx but it does not use + or - or letters. This email sent to site_archiver(a)lists.apple.com

1 0

Re: dmg from flat installer?
by Jeremy Reichman 30 Mar '10

30 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=y+8lqgognE2ZMX8BT/GXByZ9u3k=; b=o2QQrPhPO0f+a/L0mD/1ni9r97K5XU7GsMpurJSXwU6nF/RkgDuiQjvtPj38JhPVHm7jrRwJNypSwzphATLxjwtUNH5dFijue8Jt2Mn/guNdPmQInPrn6xZSD63dLi3kSA7mGoUM5DXkneox7KHpCqu0HqWsS1PfGx1COLAfQpg= Thread-index: AcrQK1FSl1Tv4LmOrkCZPqpUZcsfsQ== Thread-topic: dmg from flat installer? User-agent: Microsoft-Entourage/13.4.0.100208 If you can build your packages with The Luggage (which is really just using all of the regular tools behind the scenes, including the hdiutil bit that Greg mentioned), you can get dmgs out with: $ make dmg This runs through all of The Luggage's steps to make the .pkg and then copies the result into a new disk image which is saved into your project folder. It's awesome. A drawback is that you have to use makefiles, which can be daunting to learn if you don't know 'make' already. But you get programmatically generated pkgs and dmgs for minimal effort, you can check everything into version control, and it's mostly harmless. -- Jeremy _______________________________________________ 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: Building distribution package on the commandline
by Jeremy Reichman 30 Mar '10

30 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=hYC5F8njxg0/mgbpaZ6ksO4AsFo=; b=fBtyzfyTvSU4arWbTOI6trNSIyd5Rh1nWlEL83WEC+pTjVY8JzrKEYVxxFOet6zGwehc4h0ZEwQKi/Vm77firyRD6tut870BcIq9husssCpUvy0TcMRV0GlhbJHxYPYOV2kAj6xM4jB87/o4NbeSBVS5vvRSGRIqNKxqha2hD+E= Thread-index: AcrQKpm9k2PcSSP00UGl82wO4HgYgg== Thread-topic: Building distribution package on the commandline User-agent: Microsoft-Entourage/13.4.0.100208 If you aren't making a flat package, you could try having a distribution.dist file separately set up the way you want from the GUI tools. Build the bundle package, copy out the distribution.dist file, and stuff into your real package created with the command line packagemaker tool. Warning: I had annoying problems with the distribution.dist created by PackageMaker 3 from Snow Leopard. It produced different code from PackageMaker 3 on Leopard. The Snow Leopard-created version wouldn't run correctly on a Leopard system -- at least when I stuffed the distribution.dist into an existing package in this manner. (Did not file in Radar.) I was trying out something like this so that I could get requirements set up for a package. I abandoned this process in favor of creating not-flat packages with InstallationCheck and VolumeCheck scripts. You lose the built-in convenience functions (as far as I know you can't use the JavaScript-style requirements in these scripts) but you can create them in the scripting language of your choice (assuming those scripting languages and versions match what'll be on your expected target OSes). -- Jeremy _______________________________________________ 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: What kind of certificates to use for packages?
by Jeremy Reichman 30 Mar '10

30 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=RdtXwV74GeG6Ucmj20H1o+EsdKo=; b=qllhr83j7/CRooxrkhNYh/tLgsZhNgS+JWm8TKMGUDn88W4p4HgVKs7+3sf+r4uJ12lOLnuAV2C5BLhjeZju2AyTGcOSwY8KKW8MZeYRkyWrIkhOC/ivroNW58NwR0+R3oJPqLBJu9bq650NsPpeIUZomkzqlCGb8TqkymWlnmE= Thread-index: AcrQJ9gFdpy3fLOmBE+bScVsnYGh0w== Thread-topic: What kind of certificates to use for packages? User-agent: Microsoft-Entourage/13.4.0.100208 I would expect that a certificate signed by any certificate authority that is trusted for signing in the System Roots, System, or login keychains would work, at a minimum. Users and admins can import CAs and certificates and trust them for themselves and system-wide, respectively. Then, given my recent experience with building installer packages, my expectations are often dashed quite resoundingly even when there does seem to be documentation and precedent. I had asked something about signed packages on the Apple-CDSA mailing list on 1/27/2010 -- I know dev.iceberg was involved in that thread -- but that didn't indicate anything about any CA requirements. In that thread, Ken McLeod used a test certificate to sign a package but didn't indicate how it was or wasn't related to a CA -- or the kind of CA. -- Jeremy _______________________________________________ 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: Default file system group for /Library/LaunchAgents &/Library/LaunchDaemons
by Julian Devlin 30 Mar '10

30 Mar '10

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

RE: Default file system group for /Library/LaunchAgents &/Library/LaunchDaemons
by Glover,David 30 Mar '10

30 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcrQGEZm9y7qZtT9TIqkHryikvgfkwAABzTg Thread-topic: Default file system group for /Library/LaunchAgents &/Library/LaunchDaemons _______________________________________________ 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

Default file system group for /Library/LaunchAgents & /Library/LaunchDaemons
by Xochitl Lunde 30 Mar '10

30 Mar '10

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

Install/upgrade compatibility for package version numbers derived from VCS data
by Jeremy Reichman 30 Mar '10

30 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=MCNsqjxC95QHs8GrVOaQuihZZZc=; b=YE1qrnSl//jQf1n5UKimS/lA/a97b6r9yRjihQjlqJrZJzxoAoCMz4TBHc8AQBaZ0gcExENIWJtlgz61EZcjR1QuJ2hljrH7v4l3bpE63YmPHi+duxokKxVz/iChIJ3YZLLa6K3ehPLGdCNdMASP1rIcCHnMP9RnM7E0SBT9AjI= Thread-index: AcrQFRNKE+FNfHG8gkC0Me+TK9mLZQ== Thread-topic: Install/upgrade compatibility for package version numbers derived from VCS data User-agent: Microsoft-Entourage/13.4.0.100208 I am interested in the idea of using semantic versioning for packages I'm deploying. These packages start out from Mercurial repositories, so I can derive the version number from the semver tags ('v1.0.0') and other data from the repository to construct Really Specific Version Numbers during my automated package building process. In the following case, I use the tag plus the distance from the latest tag and the short hash of the current revision. $ hg log -r. --template '{latesttag}+{latesttagdistance}-{node|short}\n' | sed -e 's/^v//' 1.0.0+1-df34ebfc12c9 Or, I can simply get the semver tag: $ hg log -r. --template '{latesttag}\n' | sed -e 's/^v//' 1.0.0 My question: In the context of modern PackageMaker packages, would 1.0.0+1-df34ebfc12c9 be interpreted as '1.0.0' by Installer for the purpose of upgrades? I ask because I would like to use the longer, more specific version numbers for my own purposes. However, I don't want to create problems by not using something that Installer would interpret correctly for upgrades. If problems were created, I'd settle for the '1.0.0' version numbers. I want to get around to testing this but I thought I'd ask to see if anyone already knew. Thanks! -- Jeremy _______________________________________________ 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: correct way of putting InstallationCheck script
by Iceberg-Dev 29 Mar '10

29 Mar '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=yjkd0hBYYnn1cvoFFrod55ZREGKhZ504jLhkyNQuiUs=; b=e55J/NwSQ/SXKg4SfLZ17BK3DbhwvW0yupcI/Zavfho0CNNH7twV6oplqGVgaipsdY KzPguDosbMcBqnQERCWxCAg7fLCfN3/VXk1S6dLdEdcCjtGDvOJI5vKRzkz2q+0pR8H2 HaNLz4hxYi44DW07RmL9gjLLlJ6BJWCKdECho= 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=Qeqzs7xJ7raswtIA+8qZLJjQESK1+7oGQ9QfzMivXUdK9Ts/PSKsdmY3AiIWuPC7Ji /RHTKnaEuuVNWHqYiFbCA1iU7CL5PiHUE6Kjf+bfkiqEW+IZBvehg96FQovnMqGuHWvH np6F8sR7F2AEI5vEpUNugxH8eTpVOCrv2Geyo= _______________________________________________ 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 first try to add the InstallationCheck script after having built the package/metapackage without it in order to be sure that it works fine. On Mar 29, 2010, at 6:38 AM, spondita Madhuri Neog wrote: I have selected minimum target as Mac OS X 10.3 and did not specify any requirements in the "Requirements" tab.But still the InstallationScript is not getting called. Please specify whether the drag-and-drop method in "raw editing mode" is the correct way of including the InstallationScript into the metapackage.I have included the InstallationScript in the component packages using the "Scripts" tab. However I have no clue how to add the same to the Resources folder of the metapackage.I have simply used drag and drop method. This email sent to site_archiver(a)lists.apple.com

1 0