Re: migrating to new backend format

[seth vidal <skvidal phy duke edu>]

>  1. Have the gconf path contain ~/.gconf26 in front of ~/.gconf. 
>     In principle, this means that the two will be merged. Unsetting 
>     a setting should nuke the setting from both.
> 
>     Downsides: not well-tested, and creates a permanent efficiency 
>     hit as operations will always check with both backends.
>     Possible extreme weirdness if you log in to GNOME 2.4, change 
>     things in ~/.gconf only, then back into 2.6 and suddenly 
>     have both backends.

How do you resolve conflicts b/t them? Does one win over the other?

>  2. Do a one-time migration (dump/load) from ~/.gconf into the 
>     new ~/.gconf26 (probably the trigger to the migration is that 
>     ~/.gconf exists and ~/.gconf26 doesn't).

How about you do this and you tag a migration file in .gnome2 so that if
'migrated_to_gconf26' exists then it won't try the merge again.

>  3. Screw it, you have to reconfigure gnome 2.6 from scratch.

No. This is not an option imo - since all evolution and galeon and
epiphany, etc configs are in gconf there will be no end of sufferring if
my users have to reconfigure all of their settings AGAIN, considering
they just did this from gnome 1.4 to gnome 2.2

-sv