January 2011 - Installer-dev

RE: patches in PackageMaker3
by Jasper Leemans 28 Jan '11

28 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acu+p5DIysUJ0WUQS+uT8eMwJgj2tAAKm+MA Thread-topic: patches in PackageMaker3 _______________________________________________ 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

patches in PackageMaker3
by Jasper Leemans 27 Jan '11

27 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acu+ItkUyX0ESnZNTt2WPJZlJu3hCw== Thread-topic: patches in PackageMaker3 _______________________________________________ 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: Can apps packed with PackageMaker be distributed via the Mac App Store?
by Greg Neagle 25 Jan '11

25 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Sorry - to be clearer: you'll have to package your apps differently for the Mac App Store. -Greg On Jan 25, 2011, at 12:17 PM, Greg Neagle wrote: > The answer is yes. For more info, you'll need to become a registered Mac developer and pay your $99/year fee. > > -Greg > > On Jan 25, 2011, at 11:47 AM, Chris Markle wrote: > >> (If this is the wrong place for this question happy to be re-directed >> elsewhere...) >> >> Starting to think about distributing some of our free apps via the Mac >> App Store. They are currently packaged with PackageMaker. Are we going >> to have to package them differently for App Store distribustion? >> >> Thanks in advance. >> >> Chris >> _______________________________________________ >> 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/greg.neagle%40disneyan… >> >> This email sent to greg.neagle(a)disneyanimation.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/greg.neagle%40disneyan… > > This email sent to greg.neagle(a)disneyanimation.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: Can apps packed with PackageMaker be distributed via the Mac App Store?
by Greg Neagle 25 Jan '11

25 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com The answer is yes. For more info, you'll need to become a registered Mac developer and pay your $99/year fee. -Greg On Jan 25, 2011, at 11:47 AM, Chris Markle wrote: > (If this is the wrong place for this question happy to be re-directed > elsewhere...) > > Starting to think about distributing some of our free apps via the Mac > App Store. They are currently packaged with PackageMaker. Are we going > to have to package them differently for App Store distribustion? > > Thanks in advance. > > Chris > _______________________________________________ > 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/greg.neagle%40disneyan… > > This email sent to greg.neagle(a)disneyanimation.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

Can apps packed with PackageMaker be distributed via the Mac App Store?
by Chris Markle 25 Jan '11

25 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com (If this is the wrong place for this question happy to be re-directed elsewhere...) Starting to think about distributing some of our free apps via the Mac App Store. They are currently packaged with PackageMaker. Are we going to have to package them differently for App Store distribustion? Thanks in advance. Chris _______________________________________________ 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: Expected behavior for upgrades with changed file locations
by Greg Neagle 25 Jan '11

25 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Generally speaking, files that exist in the payload of version n of a package that do not exist in the payload of version m (where m > n) of the package (where both packages share the same package id) are _removed_ when version m of the package is installed. That's the intended behavior. Your mention of "local domain" has me a bit confused though. If by this phrase you are referring to the /Library/LaunchAgents and /Library/LaunchDaemons directories, then what I wrote above still stands. Things may (will) get more complicated if/when the installer writes to a user's home directory. Pre- and post- scripts should be avoided except when absolutely necessary, if for no other reason than they are frequently written with assumptions that are incorrect, especially when the package is installed by a method other than a user double-clicking it to run it interactively with Installer.app. Bad assumptions on the part of the script writer are the #1 reason packages fail to install correctly in an InstaDMG workflow, via the command line, when at the loginwindow with no GUI user, and when applied to a non-boot volume. -Greg On Jan 25, 2011, at 10:51 AM, Jeremy Reichman wrote: > What is the expected behavior for upgrades of existing packages -- > specifically packages in 10.4 format -- that have changed file layouts > since the last version was installed? If there is a difference in behavior > for packages in 10.4 vs. 10.5 format, I'd be interested in knowing about > that. > > For example, let's say package version 2.1 installed a LaunchAgent in the > local domain, but version 2.5 no longer needs that and does _not_ come > with it in its package payload. Version 2.5 happens to install a local > domain LaunchDaemon instead. Both packages have the same ID. There are no > installer components or user choices available. Without any scripts, would > the upgrade of version 2.5 over 2.1 be expected to remove the > no-longer-in-payload LaunchAgent or not? > > I have seen plenty of examples of installers removing (as well as adding, > obviously) files during upgrades, but I haven't investigated whether those > removals were driven by scripts or the package payload. I tend to see a > lot of talk about reliance on scripts for upgrades and I want to know > whether that is really necessary or not. > > 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/greg.neagle%40disneyan… > > This email sent to greg.neagle(a)disneyanimation.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: Expected behavior for upgrades with changed file locations
by Eli Bach 25 Jan '11

25 Jan '11

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:subject:mime-version:content-type:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=QLbW4CGw5fMYabAgxmrUNUPp8pCZTj+TjYj9lAQj1a4=; b=P5rjNqUoFQXNlJTFYUycNDn8dP8xHLjqd/HqhVfOrqsqeTWFGxkPGHPtPA7l3Rq/m0 xxQdAgP9Fd1H+0IOF3I5TvCPt9tQHxtoOgea6B8GTfpXUd0BQdoYRXTYeq76saMmYXhY 3K+l8uGx2PgyiNjfq5RROtzv8lQfso8/AGf9E= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=U3BbbW26oV1x59M1vUlYiyIlFejzZCvqiRcF1+s14IParNra5FIPuFKKGFbHZK79ft ut41XMa2od1SdHxYMsp49l2KjKgVAMhv1a4WaYL7XNdyQZE5w2erxnY3Gd8uhawW1SHw WIZnuRJ2Era2e3FIA+x8ctXwiddV//C5DrD0o= On Jan 25, 2011, at 11:51 AM, Jeremy Reichman wrote: > > I have seen plenty of examples of installers removing (as well as adding, > obviously) files during upgrades, but I haven't investigated whether those > removals were driven by scripts or the package payload. I tend to see a > lot of talk about reliance on scripts for upgrades and I want to know > whether that is really necessary or not. > Yes, scripting is the way to go for doing these kind of changes. And note that 'local domain' is much easier to do in a reasonable way from the application and not from the installer, for things like: -multiple users -FileVault home directories -users created after your package was run -remote user directories [where user folder isn't available until they log it] -and even more! _______________________________________________ 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

Expected behavior for upgrades with changed file locations
by Jeremy Reichman 25 Jan '11

25 Jan '11

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=nYsFw8i/GVd8r8mmD51Gpx5tfPs=; b=KZPrmODIxsC1oT8LD7advmr7bllpINq2uws2/hTQvKxzAojvJWMApa3mvKilmD5U2SXuUcJPgN4say3qYvneHJtNxRK6LupdQVqQmMGI6ZmgxInylVGWokijouj9iGDuVwfDFSSY6wgM8GwpqOKO6VChbFzK8+uQ4cXCLAgKpc8= Thread-topic: Expected behavior for upgrades with changed file locations User-agent: Microsoft-MacOutlook/14.2.0.101115 What is the expected behavior for upgrades of existing packages -- specifically packages in 10.4 format -- that have changed file layouts since the last version was installed? If there is a difference in behavior for packages in 10.4 vs. 10.5 format, I'd be interested in knowing about that. For example, let's say package version 2.1 installed a LaunchAgent in the local domain, but version 2.5 no longer needs that and does _not_ come with it in its package payload. Version 2.5 happens to install a local domain LaunchDaemon instead. Both packages have the same ID. There are no installer components or user choices available. Without any scripts, would the upgrade of version 2.5 over 2.1 be expected to remove the no-longer-in-payload LaunchAgent or not? I have seen plenty of examples of installers removing (as well as adding, obviously) files during upgrades, but I haven't investigated whether those removals were driven by scripts or the package payload. I tend to see a lot of talk about reliance on scripts for upgrades and I want to know whether that is really necessary or not. 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

patches in PackageMaker3
by Jasper Leemans 21 Jan '11

21 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acu5ajYc86x+015JRiCwpzOl+g+BgQ== Thread-topic: patches in PackageMaker3 Hi everyone, I'm trying to figure out how the "patch" options works in PackageMaker 3. I start off with a new PackageMaker project, fill in the package identifier the same as for the initial installer, the package version goes up one number (1.0.3.2 -> 1.0.3.3), I select the new .app and the old one under "patch", PackageMaker then calculates the difference and this seems to work OK because the patch package is only a few megabytes (only one dylib was changed in the app bundle). Now when trying to install the patch on a computer were the original installer was ran, I get the error "A previous version of the install could not be found". Googeling this string returns nothing useful, nor does searching the apple mailing lists. My app is definitely there, in /Applications (default). I think it might have to do with the "Realocation" option under "Components", I turned reallocation ON and in the reallocation options I do a combination search in /Applications for my app. The identifier field I filled in the same identifier as for my .app (CFBundleIdentifier field in Info.plist), but is this correct? Should it be the package identifier instead? And do the min/max version numbers have to be filled? Are they the package versions or the app versions (again Info.plist). I'm confused, tried all kinds of combinations, still can't get the patch to install!!! Any help appreciated, Jasper _______________________________________________ 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: Call a javascript function from onConclusion pkg-ref's attribute
by Bill Coderre 19 Jan '11

19 Jan '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com No, you cannot do that. onConclusion takes constants like "RequireRestart" etc. What are you trying to accomplish? On Jan 19, 2011, at 1:00 PM, Youssef wrote: > hi there, > is it possible to call a javascript function from within onConclusion attribute of pkg-ref in distribution.xml? > for example , can I make a call to "checkIfWeShouldRestart()" function like this: > ... > <pkg-ref version="1.5" auth="Root" id="${project1}.pkg" installKBytes="${size}" onConclusion="checkIfWeShouldRestart()">file:./Contents/Packages/${pr2}</pkg-ref>.... > > I did some test, but my function was never called ! did I miss something ? > > thanks in advance. > > --many > _______________________________________________ > 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/bc%40apple.com > > This email sent to bc(a)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