Understanding Metapackages vs Distributed Packages
Understanding Metapackages vs Distributed Packages
- Subject: Understanding Metapackages vs Distributed Packages
- From: Robert Kukuchka <email@hidden>
- Date: Tue, 4 Mar 2008 12:58:57 -0800
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,
and if that's what I want to do.
My Current Distributed package:
------------------------
Benefits to my solution:
- logical branching for certain items based on installation version.
Meaning I can choose to install only certain packages for 10.4.11, or
10.5.2, etc...
Drawbacks:
- inability to simply launch a 3rd party installer and have it run
without caring about what's inside. I don't want to have to update my
installer if the 3rd party installer updates a script, etc..
- inability to link EULA's to specifically installed content
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? Any help
would be greatly appreciated on this matter.
Cheers
Rob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden