site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com Hello there, Thanks in advance, Tierlieb _______________________________________________ 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... I got a slight problem using PackageMaker (XCode 3.0 on OSX 10.5.2). Currently, I am doing some integration work, like automatically setting up WebDAV shares and installing IMAP accounts. These scripts are all done with Automator and are .app files (folders, actually). I am trying to build the installer for these tools (and this is, to me at least, much more complicated than programming). The plan was to have the installer start both scripts, which then will setup WebDAV shares and IMAP accounts. I found out that I can either use an absolute path or refer to a component. Since I cannot be sure the tools will already be installed, I opted for making them components by adding them to the package, installing them and then executing them. I take it one uses PackageMaker to build packages on a Mac. I also guessed that Package Maker is PackageMaker.app, which may be a wrong assumption and I should use the command-line tool instead. There is a short guide to PackageMaker in the Apple Developer Connection pages, which I followed. There is also a lot of information at least two years old (April 2006, way before XCode 3.0) in the "Software Delivery" part of the ADC. Yet I have not found a solution to my problems: I'll recap what I did: 1. Start PackageMaker.app ("PM" from here on). 2. Enter company information 3. Drag and drop the two Automator apps into my new package (which is now called meta package, I guess, because it contains two new packages) 4. Set the ownership on these two packages to root:admin 5. Set the installation path to /Applications 6. Select the actions menu for the meta package 7. Add two postinstall actions: 7a. Action: Open file 7b. Type: Component 7c. [Select one of the programs] 8. Click 'Build and run' Here is what happens: a. The installer starts building, no errors b. I get prompted for the admin password c. I get prompted to select a harddrive for the installation, I am informed that the installation will take up 1020kByte d. After the installation finishes, I am stuck with two applications installed that take up 0kB according to Finder and 136kByte according to my terminal. e. Trying to execute these, I am informed that these programs will not run on this architecture. Since they work otherwise, I take it this is just a somewhat misleading error message for a broken file. f. The postinstall actions were not executed Here are some variations I tried but to no avail: i. Changing the folders from /Applications to /Application/[Toolname], to /tmp, to /tmp/[toolname] ii. Changing the postinstall actions from 'component' to 'absolute path' iii. Changing user rights from root:admin to [myUsername]:staff iv. Removing a bunch of .svn files and folders that were hidden within the apps by unselecting them in PM. Now my question: What is it I am doing wrong? I had a simple working test when I decided to use package maker. But that did just call a post-install action with absolute path. Plus the copying of files worked, so I am a bit dumbstruck here. Why doesn't PM copy the apps properly? Is that the reason why it does not execute the postinstall actions? Or may postinstall actions not be .app files? And another one: Is PM the right tool? Next steps include installing a normal program, deleting the tools installed (I would have loved to run them without installing, but that seems to be impossible), installing a PrefPane and a cron job. Can PM do this at all? Or is there a commercial tool better suited for the job? This email sent to site_archiver@lists.apple.com