site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Feb 5, 2008, at 4:00 PM, Michael C. Silva wrote: It's probably a good idea to file a bug report against this. _______________________________________________ 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... After further investigation, it seems that the pmdoc xml's have a version hard-coded into them for each framework or app in my project. <component id="com.savantav.AVComponentXML" path="/Re\ lease/packageFS-Frameworks/component/avComponentXML.framework" version="14"/>< But when I build my code, I use a script to compile everything then I run the PackageMaker from the command line: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker --doc SingleInstaller.pmdoc --out foo.pkg the binaries have different version numbers, but PackageMaker seems to be inserting the one it has in its XML. So, how can I build a package from the command line that respects the actual version numbers of the frameworks & apps I have? Or, what I am doing wrong? Indeed, the version value is created when you add your component to the package project. I wouldn't bet a lot on the ability of it getting updated when you build your package through the command line tool as there doesn't seem to be any obvious argument or option to do this. I'm wondering if this value gets updated when you build the package manually through the UI. I haven't checked that. This email sent to site_archiver@lists.apple.com