site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Oct 13, 2009, at 8:12 AM, Sidney San MartÃn wrote: Thanks, Kevin. I'm not seeing this option in the PackageMaker UI, and if I create a component but leave its contents empty, PackageMaker spits out a warning and doesn't include it in the built package. Am I missing something? Kevin _______________________________________________ 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... On Fri, Oct 9, 2009 at 12:35 PM, Kevin Brock <apple@kevin.com> wrote: It's possible to create a script-only target. Put one as the first component, and one as the last. It's a hack, and you'll see that target in the GUI when the scripts are run, but it works. I really wish they'd either kept the global pre- and post- or let us define our own actions to extend what's possible in the actions pane. It's not an explicit option. You can create an empty folder, add the folder as a component, but mark the folder as not to be installed. You can add scripts to the component which will be run, even though nothing from the component is getting put on the disk. Another approach is to make sure that your first and last components are things which will always be installed, and put your pre-install script as the pre-install for the first component, and your post- install as the post-install for the last component. It's a hack, but so are script-only targets. This email sent to site_archiver@lists.apple.com