Re: How to include a distribution script flat package in another distribution script project?
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=nOjaic/3d6m6NBtYRa7yPxthSKaEuoeeDWrbOJ9ZZuM=; b=ON95lAWUvPkDeLNcE0p/AV8cCeEOe3NqoiqbbJqs/mCLbnDiS3Suso1B2ICrR5PilN pWMSeSP16tHW3ez/cBmIVBGIMZALdIh4zY1Y+ChlKwUCvQAuZhI70JHgB5nwqBnEi6tB fbMaaPri4L0SF4bZtC7YKcGWdVbJBGkjCjqm8= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=bb6kwyIhh7k5k0CvKxZX2tFUMKW6+SwLsYWz36xR4vxPKQkeQrKyT3GhawN7NXB0a3 gn9G9Z/UJveNJQZSc99UAJC2VyB1bDCogO6CHzB6S5Vh0XzK4f56toRMT0LKfXd61Stm ut/3rc2anB/7Im6W38QelJSzryV2qNloa/CMg= 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. Packages are mainly payload containers. 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.? _______________________________________________ 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... On Sep 3, 2009, at 5:18 PM, Kennedy, Smith (Macintosh Software - IPG MCT) wrote: 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. 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. 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. This email sent to site_archiver@lists.apple.com
participants (1)
-
Iceberg-Dev