Re: How to include a distribution script flat package in another distribution script project?
Re: How to include a distribution script flat package in another distribution script project?
- Subject: Re: How to include a distribution script flat package in another distribution script project?
- From: Iceberg-Dev <email@hidden>
- Date: Thu, 3 Sep 2009 23:24:26 +0200
On Sep 3, 2009, at 5:18 PM, Kennedy, Smith (Macintosh Software - IPG
MCT) wrote:
On Sep 2, 2009, at 3:32 PM, Iceberg-Dev wrote:
On Sep 2, 2009, at 7:25 PM, Kennedy, Smith (Macintosh Software - IPG
MCT) wrote:
Hello,
[...] my E.pmdoc, even though add C and D to the project, D comes
up as a
question mark. When I build E.pkg, it includes C but not D.
Is there something I am doing wrong or is this just outside the
capability of distribution scripts? If the latter, then it seems
that
distribution scripts are less capable than metapackages to create
installers where a large number of software components need to be
gathered together.
You can not have a distribution script as a component of another
distribution script.
I was hoping I just didn't know what I was doing, rather than it being
a limitation of the distribution script technology. This is really
disappointing (I'm sure I am not even remotely the first person to
voice this, given the age of distribution scripts). I hope this is a
foolish oversight rather than a "feature" (conscious decision made by
the designers) intended to prevent the re-distribution of other
packages. If so, it is a lousy way to implement this. Deciding
whether a package should be re-distributable or not is a policy
decision best decided by the developers using PackageMaker to deploy
their software.
With the distribution script "format", a distribution script is just
a XML file describing the hierarchy of packages, their requirements
and the potential dependencies between each other.
Packages are mainly payload containers.
So as long as you have access to the Packages and the distribution
scripts, merging them is not impossible. It's a bit like having
access to 2 source code (the scripts) and libraries (the packages).
You need to merge the 2 distribution scripts into one.
How does one go about doing that? Does that mean I need to merge
D.pmdoc and E.pmdoc? If so, and I don't have access to D.pmdoc
because it comes from someone else (third party who isn't sharing),
what are my options aside from doing a "pkgutil --expand" etc.?
You don't need to. Just extract the built packages and add them to
the project (it's possible though I tend to remember it's not
obvious). Then you need to analyse the distribution script and see
what you need to add to your project.
_______________________________________________
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