Installer project directory clarifications
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 1.5.0.10 (Macintosh/20070221) So my two questions are: Thanks, Mike _______________________________________________ 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 want to make a single-package installer that contains all my product's files but I also want to be able to have that package be deliverable in a Managed Install via Apple Remote Desktop 3. The Software Delivery Guide is a little unclear as to exactly which installer packages can and cannot be delivered via this method. In the fourth chapter it says "Packages contain a product or a product components", but then later on page 31 the directory hierarchy appears to require a separate "component" directory for each component in the install. What if I only want one package but multiple component directories in that package? 1) What is the proper directory hierarchy for a single project directory full of a variety of product files for a single package and 2) is the directory hierarchy listed on page 31 mandatory - that is, does the installer actually read the directory hierarchy and then execute the other items such as "extras" at runtime? This email sent to site_archiver@lists.apple.com
participants (1)
-
Mike