Re: Understanding Metapackages vs Distributed Packages
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Mar 4, 2008, at 9:58 PM, Robert Kukuchka wrote: _______________________________________________ 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... Hello all, Sorry for perhaps some mundane questions, but I'm trying to understand the solution that works best for me. Currently I've made a Distribution package with PM 3. Unfortunately a number of our installation items are 3rd party packages (or in some cases metapackages). As far as I'm aware PM 3 packages are distributed packages, and thus cannot support metapackages. I'm trying to determine if it's possible to make a metapackage installer in Leopard Yes, just target Mac OS X 10.3 (Panther) in the Alert sheet that appears when you create a new project (you can call it back later through the menu bar). I'm thinking that a metapackage might be a better solution but how can I mimic the logical branching of a Distributed one. I ONLY need the ability to mark an installer as valid or not based on system version being installed in. I guess this could be done with a script? Yes, just exit with 64 to disable the package. It's not as flexible as a distribution scrip, yet it's less complex to manage. This email sent to site_archiver@lists.apple.com
participants (1)
-
Stéphane Sudre