site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dear packagers, That said, this is how far I've come without the GUI. The command There are a couple of issues now: Helpful comments and suggestions most welcome ;-) Many thanks, Oliver _______________________________________________ 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... due to the buggy GUI version of PackageMaker 3 I'm resorting to the command line utility in order to build my packages. I'm also trying to avoid those pmdoc files completely because they are regularly corrupted by the GUI. packagemaker --root payload --id com.example.MyTools --version 1 -- scripts scripts --target 10.5 --domain system --out MyTools.pkg -- verbose successfully builds my package. Here "payload" contains a huge number of files and folders (owned by root:wheel) I want to be deployed at / usr/local/MyTools. The folder "scripts" contains a single file called postinstall. 1. How can I specify the destination path /usr/local/MyTools? Obviously the installation fails because Installer doesn't know that this is where I'd like my payload to be dropped … 2. How can I add a little descriptive text to be displayed in the Installer's welcome window? 3. How can I check for the existence of a file on the target volume prior to installation? The man page of packagemaker tells me this could be done with a script called InstallationCheck, however, I have no clue about its content and where to place this script. 4. How can I build a package with several installation choices? My understanding is that I'll need a metapackage for this … but how to assemble it on the command line? This email sent to site_archiver@lists.apple.com