site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=A0iRI3t6pKZw3eUAAqqb8BnOu/M=; b=Mt8a+/XzGCOud5/kCCK620hYLqCnuAMBdjRgqtz1oM8UotAe5kenUPZnYnxDDBQdKxctpzhpXtSjPexfFrJYzL4fm/UlygeUY88yWR16N4EoB8YIlmCyaNT+C6wDsSTXFZT7Vy3YQHaFqM3sXsNpQ7JtLbjmso0dpNYkV6f1tDk= Thread-index: AcrEWdIhPgz1W5wgIkGWh656dFToQA== Thread-topic: Build metapackages from the command line with PackageMaker 3 User-agent: Microsoft-Entourage/13.3.0.091002

Actually I had a pmdoc that I tried to use on the command line and it still gave me an error. I wasn't able to get it to build on the command line even with the pmdoc. Maybe I didn't get the parameters quite right, but there aren't that many parameters when building from a pmdoc.

I think I've tried building a metapackage from the command line with a .pmdoc, and couldn't get that to work, either. However, the likely culprits are the third-party packages I'm trying to include in the metapackage -- they are old-style .mpkg bundles with .info and .list files. They lack Info.plist and other modern niceties. I also had problems trying to import these two architecture-specific installer packages into Iceberg. One almost imported, but I had added an Info.plist of my own creation into the bundle as an experiment. So, the only metapackages I've been able to build successfully from the command line under Snow Leopard are the same -- they have bypassed PackageMaker 3 entirely. These work swimmingly, but I wouldn't be surprised if pkgutil throws fits later. -- Jeremy _______________________________________________ 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... This email sent to site_archiver@lists.apple.com