site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Jul 30, 2008, at 12:22 AM, Jim Wrenholt wrote: On Jul 29, 2008, at 5:01 PM, Stéphane Sudre wrote: On Jul 29, 2008, at 10:46 PM, Jim Wrenholt wrote: Multiple questions: 10.4 or greater the Info.plist in the application bundle of the payload. Maybe nothing? When using ARD, this kind of interaction is not possible. The way I see it, you have different solutions: (b) you can _not_ modify the application. In both cases, I would use a second package: - in case a, it will install the files at the specific location. My $0.02 _______________________________________________ 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... I would like a lab administrator to download the package, and change a couple of items in the payload's Info.plist, (i.e. provide path names) and then use Apple Remote Desktop to distribute that package to client computers. The payload is a single application. Without installing the package, I don't see how to allow the admin to set the path. But once it's installed on the admin computer and the path is set, it's no longer in the package for easy delivery to the client's machine. This software will be used in elementary schools so letting the client-user set the path after installation is not workable. I'm a still a newbie to Package Maker. So, any advice would be appreciated. - which OS do you target? - which Info.plist file are you referring to? The one of a bundle package or an application bundle in the payload? - What prevents you from doing this work in a postflight script? So, the script would need to query the path from the admin, before mass distributing it to the clients. And then modify the payload's .plist on each client machine as part of the install in a postflight script. I don't know if that is possible? (a) you can modify the application itself. Then a solution would be for the application to look for potential default settings in a specific location such as in /Library/Application Support instead of relying on changing values in its Info.plist which is not a good solution when you consider code signing. - in case b, it will look for the application and then update its Info.plist. You need to see this as an updater (use a locator and a specific bundle identifier). The package can be created by the lab administrator if you provide a pre-configured PackageMaker project so that he/she just has to change data in the new Info.plist and build the project. Then it can be installed on the remove client computers after the application package has been installed. This email sent to site_archiver@lists.apple.com