site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com _______________________________________________ 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 <installer-dev-bounces+xochitl_lunde=tripplite.com@lists.apple.com> wrote on 03/10/2010 09:31:38 AM:
I've come across other posts about this in the archives and on the 'net, but
have not found a solution, so I'm going to ask again.
Has anyone been able to use the backwards-compatible mode of PackageMaker
3's command line tool to build a metapackage installer? If so, I'd like to
know the magic to make it work without having created a .pmdoc first.
When I try to build such and installer, I get this:
$ PACKAGE_TITLE="Insert metapackage title here"
$ /Developer/usr/bin/packagemaker -build -ms "./packages" \
-p "./build/$PACKAGE_TITLE.mpkg" \
-i "./Info.plist" \
-v
Building in backwards compatible mode
ERROR: No packages to build.
[Fwiw, I've filed this as <rdar://problem/7728789>, because it happens with
every metapackage I try to build with any selection of pre-existing
sub-packages.]
I'm trying to use the backwards compatible mode of
/Developer/usr/bin/packagemaker so that I don't have to generate a .pmdoc
file with the GUI PackageMaker first. It appears that PackageMaker 3's new
command line options would allow building metapackages if a .pmdoc was
present, but I can't see a way to use those new options without having a
.pmdoc first.
Thanks!
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. xo