Re: handling configuration files
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=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; bh=NkUNtx67QGliaR25PiBr4rHTb2xnZQekcEhpcwxkg7Y=; b=du220eqYYR0zn8/q4SlyMdnx9fKRvC61lPAAafyNYgZIyoYHzh4sVsMSIeCsBbd7s7 D3oSO08aQy6pZ4gWJkRLHC/fGnZZlpadSto4w9D3osUcpiQBOTFKBF76a+dXlWfLyJDB dPx1h9jXhcHhzpTfxPWmiEInaIgjepumClQv4= On Jul 6, 2011, at 2:17 AM, Joe Damato wrote: 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. What does you requirement look like? 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? _______________________________________________ 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... Requirements should word to accomplish this (I'm not saying it's the best solution). Now it depends whether the requirements you get when you build your package is correct. I somehow remember there was a hidden option or key for this with bundle packages. But this would require checking the mailing-list archive. This email sent to site_archiver@lists.apple.com
participants (1)
-
Iceberg-Dev