site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:content-transfer-encoding :message-id:references:to:x-mailer; bh=Tspj/UDNlEKDsOPs72Opla/tqdBJxEAYZncjxNDCEkc=; b=loa/KahwDTtVXvXUnEWGXqdhL+pi8bQ8UK3PDypQI3jLJ1ve3E3yGG1Qpt8N2JKKyL UiyLeuez2YzRnOKUcpv2w19+1oZ79HVF/GmPYYnN5Ibe/71xPDph28vNMdBlfQrBFH3I HH/oRT6Y+/2eqRJJ9+2ntSJtOsGO7NGUGIRwI= 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=hHuOJUF3lHw++PlsAOe8h1mFQxy4U5dXcIdCFaVZAQu1Ip9MI0zJHiDCBbpgxDgv0G eXnkRemmgm2NL0UTSWYHlPFASidm13uSVtOBnL8wC2a+RkIFrzqiG81qJZJALOp7+62b /fZ/IjBeQ0IAPwI8bouzBOGBIQf7R9vuHew9w= On Sep 1, 2010, at 4:58 AM, hagen wrote:

Hi All, I've got a rather big packagemaker installer project. Whenever I load the project into package maker the permissions of the references to the files to be installed are re-set. And I have to manually step through and apply recommendations (since I have corrected the permission on my installation). Not only is this really tedious and error prone it also sometime just don't set the correct permissions in the install package. After installing (on a clean machine) the permissions are still messed up.

1. How can I workaround the permission issue? (Do I need to include a postflight script correcting this?) 2. How do I provide an uninstaller? 3. Where are the information stored, about which software and the corresponding versions are installed? So the OSX installer knows when to indicate "upgrade"? 4. Actually I generally tend to use OS provided technologies, for many reasons, but should I better use another install maker? packagemaker seems to be very buggy, it often crashes (most likely after a lengthy attempt to reset the permissions, but any other occasion seems to be welcome). 5. Why is packagemaker so extremely slow? Apple invented the "Instruments"? Are your developer actually using this? What are your future plans with packagemaker and which installer builder are using you internally? 6. The dependency logic for the choices seems completely broken. Only very basic logic operations do work. Any time frame for a fix?

Thanks and best regards, Hagen.

Hagen, 1. Instead of setting owner/permission stuff within PackageMaker, you should instead create a script as part of your build process to set the owner/permissions on the files that the Package references. PackageMaker defaults to the owner/permissions of the files, and doesn't seem to do a great job of remembering changes you make to the packagemaker project file itself. 2. Some people create an uninstaller application, others create a shell script, some create a text file/web page explaining where all the application files are and what to delete, while others do nothing and let the user figure out what to delete. 4. I think Apple lets PackageMaker suck so badly to 'encourage' you to not use it. 5. See 4. 6. See 4. Eli _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com