site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Are you sure it's PackageMaker which is launching it? Is there not a part of your script building a Disk Image? Side question: how do you build a meta-package from the commande line using PackageMaker? I will try to see if I'm seeing the problem on a 10.3 system. _______________________________________________ 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 mercredi, novembre 17, 2004, at 03:45 PM, Huyler, Christopher M wrote: The script does create a disk image but I added a few lines to count the number of running DiskManagementTool processes and print the value before and after each call to PackageMaker. The value printed increases after the call so I am positive that is where it is coming from. However, it inconsistent as to which call causes it. Sometimes its only one call, other times its all four calls. Here is a snippit of shell script that I use to create the meta-package: PACKAGEMAKER="/Developer/Applications/Utilities/PackageMaker.app/ Contents/MacOS/PackageMaker" PACKAGE_DEST="/Users/huych02/package_stage" PACKAGE_FILES="/Users/huych02/dev/Mac/package" mkdir -p "$PACKAGE_DEST" echo "Processes before : `ps -xalww | grep DiskMan | wc -l`" $PACKAGEMAKER -build \ -p "$PACKAGE_DEST/MetaPackage.mpkg" \ -f "$PACKAGE_FILES/MetaRoot" \ -r "$PACKAGE_FILES/MetaResources" \ -i "$PACKAGE_FILES/MetaPackageInfo.plist" \ -d "$PACKAGE_FILES/MetaPackageDescription.plist" echo "Processes after : `ps -xalww | grep DiskMan | wc -l`" The Info.plist files and Description.plist files were generated using the PackageMaker gui. The MetaRoot folder is empty since a meta-package has no files of its own (PackageMaker doesn't work unless a folder is specified). If I have time today, I will make a test script and package that duplicates the possible bug, zip it up, and send it to you. I tried creating both a package and a metapackage using this tool on Mac OS X 10.2.8 (I don't think it has changed in 10.3.x) and I didn't get the additional processes. BTW, using the command line to create a metapackage this way has a side effect from what I can see, this may require some additional work: The metapackage contains .bom, .pax[.gz] and .sizes files which are useless. This email sent to site_archiver@lists.apple.com