Re: How to use already-built subpackages? (Disconnect between PkgMkr, SDG docs)
Re: How to use already-built subpackages? (Disconnect between PkgMkr, SDG docs)
- Subject: Re: How to use already-built subpackages? (Disconnect between PkgMkr, SDG docs)
- From: Christopher Corbell <email@hidden>
- Date: Fri, 21 Aug 2009 14:17:26 -0700
On Thu, Aug 20, 2009 at 11:06 PM, Christopher Corbell
<email@hidden> wrote:
I'm trying to create an installer with PackageMaker 3.0.3 targeting Mac OS 10.4 and later.
There are three different components to be installed (app, documentation, config files).
I started in the PackageMaker interface just having three choices each accessing their own payload contents directly. However I got unexplained errors, warnings and general failure getting it to work properly, so I turned to the Software Delivery Guide, whcih suggested the way to do this is to build and test individual packages for each component.
So I did that, and I have three atomic packages that each contain their own payloads for the separate components, and work perfectly on their own. I put the three built packages in a "packages" directory and I'm trying to build a top-level distribution pmdoc that will incorporate them into the distribution installer.
But now packagemaker has stumped me.
FWIW, I went back to the first approach - building the components in the master distribution pmdoc directly from source - and finally got it to work. Part of the issue was the "relocatable" checkbox needed to be unchecked (found the error mentioned in the list archives - why isn't that unchecked by default)? and the other was a nil file path exception that occurred, apparently, because two components were both calling mkdir -p in a Preflight script for their same (parent) directory (a folder created inside /Applications to hold the app and optionally a tutorial).
So I got it working but it feels pretty fragile, and perhaps most disconcerting is there is no way to test the subpackages individually as is recommended in the SDG, unless just by making them all enabled for custom install and enabling one at a go. If anyone knows of a way to use PM3 to assemble a distribution from already-built component .pkg's I'd still love to know - or even if it's just possible from the command-line packagemaker. Otherwise, all that stuff in the SDG needs to be rewritten to match how the tools behave.
- Chris
_______________________________________________
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