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

Re: How to replace old version of product?
by Bill Cheeseman 23 Jun '08

23 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcjVLvekrl3l/kgpReC/0ygrUSEd7wAII8cQ Thread-topic: How to replace old version of product? User-agent: Microsoft-Entourage/12.10.0.080409 on 2008-06-23 8:45 AM, William J. Cheeseman at bill(a)cheeseman.name wrote: > I have everything working nicely -- except that my installer won't replace > an older version of my product if it finds one installed. > > I assume I have to configure the Patch button in each component's > Configuration pane. Or do I simply have to write a preinstall script and remove older versions of components myself? It seems odd that the documents don't say anything about this, although Stephane Sudre's old How-to article about an earlier version of PackageMaker says as much. I guess that would provide the flexibility needed to deal with different names and configurations in older versions of the product. But how does that fit in with the ability to allow or prohibit downgrades using a simple checkbox? If PackageMaker/Installer can tell by itself how to prohibit a downgrade, why can't it deal by itself with an upgrade? And then what is the Patch button for? -- Bill Cheeseman - bill(a)cheeseman.name Quechee Software, Quechee, Vermont, USA www.quecheesoftware.com PreFab Software - www.prefabsoftware.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

How to replace old version of product?
by Bill Cheeseman 23 Jun '08

23 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcjVLvekrl3l/kgpReC/0ygrUSEd7w== Thread-topic: How to replace old version of product? User-agent: Microsoft-Entourage/12.10.0.080409 I have everything working nicely -- except that my installer won't replace an older version of my product if it finds one installed. I assume I have to configure the Patch button in each component's Configuration pane. But I can't find any instructions about how to do that. The Save button is only enabled when the text field is empty. It remains disabled no matter what I type into the field, even the path to the product ("/Applications/Event Taps Testbench.app"). The instructional text in the Configuration pane, "No patch root selected," means absolutely nothing to me -- what is a patch root? I can't browse for an older version of my product because I don't have one just lying around. I chose FireFox just to see what would happen, and "/Applications/FireFox.app" appeared in the text box and the Save button became enabled. But the moment I try to edit it, the text field reverts to empty. And what do I do if I want the installer to replace ANY older version of my product? What if some older versions had different names? I guess, until all these UI bugs are fixed, I have to install an older version of my app on my development machine just so I can drag it onto this field. Will that do the trick? C'mon Apple. You want us to deliver product for the platform, don't you? Getting PackageMaker 3 right ought to be an extremely high priority. Why do I find more than a dozen major-major bugs that interfere with its everyday use? (Still frustrated.) -- Bill Cheeseman - bill(a)cheeseman.name Quechee Software, Quechee, Vermont, USA www.quecheesoftware.com PreFab Software - www.prefabsoftware.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: Add app icon to Dock
by Andrew Li 23 Jun '08

23 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcjSqhMya8wL5eM1RWuYB/5Li9HlYQABREIgAAvaVv8AjT4VoA== Thread-topic: Add app icon to Dock _______________________________________________ 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: How to control component package names?
by Bill Cheeseman 23 Jun '08

23 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcjVDd9v3UmpEOedT9C/rexNP538Og== Thread-topic: How to control component package names? User-agent: Microsoft-Entourage/12.10.0.080409 on 2008-06-22 12:02 PM, Stéphane Sudre at iceberg-dev(a)orange.fr wrote: > You can manually change this using the FLAT Package Editor. I've avoided the Flat Package Editor so far because there aren't any instructions for it. And "Help isn't available for Flat Package Editor." So, at your suggestion, I opened the Flat Package Editor, then opened my finished installer package into it. I then changed the names of the two component packages by changing the capitalization, and saved. When I ran the modified installer, it failed because it couldn't find the software to install. I suppose I could also have gone into the generated installer script and changed all references to these names. But I kind of hate to take a chance on the modified installer working correctly out in the wild, without assurances from somebody inside Apple that this will work correctly in all respects. -- Bill Cheeseman - bill(a)cheeseman.name Quechee Software, Quechee, Vermont, USA www.quecheesoftware.com PreFab Software - www.prefabsoftware.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: Add app icon to Dock
by Andrew Li 23 Jun '08

23 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcjSqhMya8wL5eM1RWuYB/5Li9HlYQABREIgAAvaVv8AiCMiwA== Thread-topic: Add app icon to Dock _______________________________________________ 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

Bug in Requirements with Binary plist file [?]
by Stéphane Sudre 22 Jun '08

22 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com The case is the following one: - A Bundle format pkg with requirements. - One of the requirements checks a value in a plist file If the plist file is saved as a binary file, the requirement fails. This is on Mac OS X 10.4.11 with all the latest patches. _______________________________________________ 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.… Is there a known bug (it can also be unknown) with requirements and binary plist file? If the plist file is saved as a XML (text) file, the requirement is correctly checked. This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to control component package names?
by Stéphane Sudre 22 Jun '08

22 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com You can manually change this using the FLAT Package Editor. _______________________________________________ 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.… On Jun 20, 2008, at 6:22 PM, Bill Cheeseman wrote: PackageMaker 3 automatically names component packages when I add a component to a project. I can't find a way to control these names, or in particular their capitalization. For example, my PFEventTaps.framework folder is given the automatic name "pfeventtaps.pkg," and my Event Taps Testbench application is automatically given the name "eventTapsTestbench.pkg." (I can't make out the logic that causes one of them to have all its capital letters converted to lowercase, while the other has only its first capital letter converted to lower case.) This is unfortunate, because Installer displays these names as is during installation. I would rather the user see that "PFEventTaps" or "PFEventTaps Framework" is currently being installed, than "pfeventtaps." Changing the package identifier in PackageMaker has no effect. Naming the install choices has no effect, either. The latter is especially surprising, because I would have expected the editable installer choice name to be used for this purpose as well as for the purpose of populating the customize dialog in Installer. I suppose I could change the component package names via script, but I fear that this might interfere with the functioning of the installer package. Can anybody steer me in a useful direction on this? >From what I've seen, the name of the package is computed from the name of the Install From item. Side note: There's a bug in the current version of PackageMaker, otherwise it would not be fun: if you change the item and build the project, you still get the old item. You have to save the project and rebuild it to get the correct item in the payload and package). Since you're using the FLAT package format in this case, using a script to change the components name would require to edit the xar archive and the distribution file. I had a look at the .pmdoc file bundle and it shows that the names are dynamically computed during build time. Depending on the point of view, it may not be possible to use the choice name during installation. Because a choice may contain multiple packages. So if the idea is to follow the installation of packages, it makes sense to display the .pkg name. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Permissions
by Nigel Kersten 22 Jun '08

22 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-status: no signature _______________________________________________ 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: Current User or Computer Installation. (PackageMaker)
by Stéphane Sudre 22 Jun '08

22 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hello, I guess someone must have noticed this. _______________________________________________ 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.… On Jun 19, 2008, at 5:57 AM, Ismail Tabtabai wrote: The destination typed in PackageMaker is actually a string that would be attached to the "Destination Select" at the time of installation! I didn't think it was that easy. With the new format for Mac OS X 10.5 (and later supposedly), you can define an installation domain. So you can define that your components can be installed either for all users or for the current user. If you need to be compatible with Mac OS X 10.4 or earlier, this is not a solution. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Permissions
by Stéphane Sudre 22 Jun '08

22 Jun '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, The command I run is: packagemaker --root /path/to/root --id com.mycompany.myapp What are these special permissions? root:something? Could it be solved by launching the command with sudo? _______________________________________________ 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.… On Jun 17, 2008, at 8:52 AM, Martin wrote: I would like to automatically create an installer package using exclusively the command line and without PackageMaker.app and without a .pmdoc file. /path/to/root has special permissions that I wish to be taken into account by packagemaker. My problem is that the permissions are not taken into account: whatever permissions /path/to/root has, packagemaker ignores it and sets it to standard permissions. How do I tell packagemaker to keep the files' permissions, using the command line? This email sent to site_archiver(a)lists.apple.com

1 0