Re: handling configuration files
Re: handling configuration files
- Subject: Re: handling configuration files
- From: Iceberg-Dev <email@hidden>
- Date: Wed, 06 Jul 2011 21:37:05 +0200
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.
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.
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?
I somehow remember there was a hidden option or key for this with
bundle packages. But this would require checking the mailing-list
archive.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden