site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi, So I guess my questions boil down to Thanks for any guidance! cheers John Clyne National Center for Atmospheric Research 303.497.1236 (w), 303.809.1922 (c) clyne@ucar.edu _______________________________________________ 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 have some questions re installation conventions used in the Mac world when porting multi-component applications from other unices. I have an app that consists of a GUI, several command line utilities, shared libraries depended upon by both the GUI and CLUs, header files, doc, etc. I'd like to provide the package via an installer that is familiar to Mac users, and minimizes setup required prior to using the tools. In Linux, for example, the installer would be a shell script allowing the admin to specify a target installation directory. Setup would consist of yet another shell script that users could source to configure execution paths, shared library paths, etc. The notion of Mac Bundles, with their drag-and-drop installation, is obviously a much more elegant way to handle software distribution. However, it's not clear that Bundles are at all appropriate for packages composed of multiple CLUs with shared library dependencies: how would one resolve the shared library paths? 1. Are there any best practices for CLU installation? Put them in a well-known location (e.g. /usr/local/{bin,lib,include}) where they will hopefully automatically appear on the appropriate search paths, or provide the flexibility to install anywhere and use some other mechanism to resolve setup issues (paths)? 2. What tools are recommended for building an installer for a multi- component application such as i'm describing? This email sent to site_archiver@lists.apple.com