site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On vendredi, novembre 5, 2004, at 10:33 PM, John Rosasco wrote: Hello, <key>IFPkgFlagComponentDirectory</key> <string>../.containedPkgs</string> I currently have: Description.plist Info.plist resources Meta Can anybody tell me the answers to these two questions: It's not tested I've just typed it in Mail.app but you get the idea. My $0.02 _______________________________________________ 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... I'm creating a disk image from a meta package for the purposes of auto-launching installer when the disk image is downloaded from the website. I'm using the hidden packages method (with the .containedPackages directory). This is described at: http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/Concepts/sd_mpkg_anatomy.html However, this description is for PackageMaker using the UI. My Info.plist file references the .containedPackages directory as follows: In the same directory where Meta is the parent directory of .containedPackages. And, of course, the .containedPackages has all the constituent packages copied into it. (1) Is this directory structure appropriate for use of PackageMaker on the command line to create a meta package. I don't think so because when you build a Metapackage, the packages are not automatically moved/duplicated/copied to the destination. (2) Assuming the plists are correct, can anybody provide the exact PackageMaker command line to build the meta package ? I'm not sure the command line tool for PackageMaker (which is the app itself in 1.1a10 and later version) can build Metapackages. Because I just tried to make it swallow the fact that there was no root dir and the result was not that great. Anyway, assuming you have all this stuf, and you don't care at all about Mac OS X 10.1 compatibility, I don't see anything preventing you from building the Metapackage yourself: mkdir $HOME/build/ cp -R Meta/*.pkg $HOME/build/ mkdir $HOME/build/MyMetapackage.mpkg mkdir $HOME/build/MyMetapackage/Contents cp Info.plist $HOME/build/MyMetapackage/Contents/ ##echo pmkrpkg1 > $HOME/build/MyMetapackage/Contents/PkgInfo ## As this puts a 0, you need to copy a file instead cp -R resources $HOME/build/MyMetapackage/Contents/Resources cp Description.plist $HOME/build/MyMetapackage/Contents/Resources/ I have another solution which involves using a 3rd party tool which will be available this week-end but I think the solution above is the best one in this case. This email sent to site_archiver@lists.apple.com