Re: migrating to new backend format

[Havoc Pennington <hp redhat com>]

On Sun, 2003-10-05 at 16:12, seth vidal wrote:
> How do you resolve conflicts b/t them? Does one win over the other?
> 

Yes, it's a path search, now we have:
 mandatory -> ~/.gconf -> defaults
we could do:
 mandatory -> ~/.gconf26 -> ~/.gconf -> defaults

with the twist that ~/.gconf remains writable which means that key
deletions remove the key from both ~/.gconf26 and ~/.gconf. However key
writes (new values) go only to ~/.gconf26 (as currently coded, IIRC), so
if you just _set_ a new value, it changes ~/.gconf26 and leaves ~/.gconf
alone.

It's a bit hard to know how this would behave, so I'm leaning against
it.

> 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.

Right.

> >  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

I agree with you, just presenting all the options.

Havoc