[csw-maintainers] Migrating config files from /opt/csw/etc to /etc/opt/csw during package update

Maciej (Matchek) Blizinski maciej at opencsw.org
Tue Sep 1 16:42:24 CEST 2009

2009/8/25 Trygve Laugstøl <trygvis at opencsw.org>:
> Philip Brown wrote:
>> I think with this sort of thing, you have to consider the likelyhood of
>> breakage.
>> If the nature of the application/configuration is relatively
>> straightforward, and/or compatibility between the two versions is very
>> strong, then I think the best thing to do is an automated migration.
>> If on the other hand, breakage is very likely, then probably "halt and
>> prompt" is best.
>> An intermediate possibility, might be if the app has very good
>> configuration file verification.
>> Then you could do the automigration, VERIFY it, and then halt noisily if
>> it fails verification.
>> A post thought: in this case, I think you should always only copy; never
>> remove. Worse case, 'mv' old config to config.migrated or something.
> These points sounds like a good policy to me and are similar to what I've
> talked about earlier.

I wrote up a comparison, for the sake of brevity, formatted as a
table. It considers the simplest case, a single file which was
previously on /opt/csw/etc and is going to be in /etc/opt/csw.


In a simple case, which option people think is best?


More information about the maintainers mailing list