site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Andy, Responses are in-line. On Dec 21, 2005, at 9:51 AM, Andy Cedilnik wrote: Hi Luke, Hope that helps. Best, Luke Thank you. Andy Luke Bellandi wrote: Hi Andy, Check out /Developer/Tools/packagemaker or "man packagemaker" Best, Luke On Dec 21, 2005, at 9:35 AM, Andy Cedilnik wrote: Hi Luke, Andy Luke Bellandi wrote: Hi Andy, What specifically are you trying to accomplish? - Luke On Dec 21, 2005, at 9:20 AM, Andy Cedilnik wrote: Hi, So, please let me know if you have any more information. Thank you. -- Andy Cedilnik Kitware Inc. -- Andy Cedilnik Kitware Inc. _______________________________________________ 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... Ok, I guess I am missing something. On my mac the packagemaker is in /Developer/Applications/Utilities/PackageMaker.app. The man does not return anything, but that may be the version problem. On the mac mini, the packagemaker is where you said and the man works fine. You may have different versions of the Mac OS X Developer Tools installed. Try upgrading the developer tools on your Mac. Go to http://developer.apple.com for the latest download. That said, the pmsp has tones of information inside. Where should that information come from? For example, there are all the TIFPkgFlag* and various versions and so on. Should that be in plist file? Can I have a sample of that file? These keys all come from an Info.plist file. Check out the Software Distribution documentation on the ADC site: http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/index.html The article "Examining and Modifying Property Lists" lists what keys you can use in your Info.plist file and what they do. The packagemaker command line tool can then use that XML as an ingredient to create your package. It's Apple's command line interface to packagemaker. It's probably better (and easier) for you to write scripts to interface with that than to try to match our .psmp format. Our package file format is not public (and therefore is subject to change), while our command line interface is public and will remain backwards compatible. I am trying to generate PMSP files. For example, I want to automate the process of creating releases without somebody having to run the GUI. I am trying to read and write the PMSP file produced by PackageMaker. Looking into it, you can see it is a binary file and somewhere close to the beginning is a string: typedstream. I found some information about typedstream, but the most promising is the code in GNU Objective C. That said, before I go and rip a bunch of code out of gcc, is there any simple explanation on the PMSP file format? I figured out all strings have length prepended, but there is much more that is changing. Also, (question for the apple guys) is there a problem with reverse engineering pmsp file? Will it change anytime soon? Andy _______________________________________________ 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/luke% 40apple.com This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com