site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=MW20gQKk2jSu9+K36wopNXaGF2/Lozg4gK4yng3KtlQ=; b=K9nJoxt79ExTL3BJAaNMELKFl5O0kNLZbuj4xLdHO0q9XYIRE4F1obTvr9mfw61K3X Es3GNIX16omjshPFg70YyfytPE4jzTo8WuyM+04TiHVEznm6CJSENllWFbrkFxVtu9Zg mJ/jvw66W/fVP+4ASq5Xx3Ufew7v+Rfd38gUs= Hi - The application I'm trying to package comes with a set of default configuration files and plists, however, these files are modified after installation via postinstall so that they suit the user's system (for example, picking a network interface or how much RAM to use for a specific data structure, etc). When the user installs a new version of the packaged application, these configuration files are overwritten. I tried using requirements to test for the existence of the config files and if they exist, skip installing one of the contents that contains the config files, but I was unable to get this to work properly. Doesn't seem like requirements were intended to be used like that. Any hints for dealing with config files? I've seen package management systems in other environments that allow you to mark a packaged file as a config file so that it is not overwritten on upgrade. Maybe something like that is possible with package maker and I'm missing it? Thanks, Joe _______________________________________________ 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... This email sent to site_archiver@lists.apple.com