site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com I received the following. Q2. To preserve Resource forks, what about using the -s option. thanks rich But, I want to invoke PackageMaker from the command line. The issues I face are: -- Sincerely, Rich Kubota rkubota@apple.com (408) 974-6212 _______________________________________________ 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... Q1 - Is there an undocumented command line packagemaker option to manipulate the file permissions as he asks below. Seems like he should be able to do this himself with a script better than packagemaker could do. As part of our daily development routine, I have a machine that, once a day, builds my application using the most recently available source from my repository. This is all accomplished automatically using shell scripts triggered from a launchd task, and this has worked well. I now need to take my built application, and automate the production of an installer package into this daily routine. I have a .pmproj file that I have used periodically to build the package. Using the PackageMaker UI, everything works fine. 1: I cannot set the recommended file permissions for the installer sources from the command line via PackageMaker. 2: I cannot preserve resource forks without authorizing, which can only be done via the UI. I do not want to work my way through each file/directory individually for step 1, my app contains 2738 items. This is subject to change daily and would be a major headache to maintain a matching script. Is there a way to accomplish my goals? Are there some undocumented command line switches for Package Maker to achieve this result? Is there a shell script you can share that will set the permissions? If necessary I can convert my resources to data fork based files, so (2) has a workaround, but I hope you have a better one. This email sent to site_archiver@lists.apple.com