Re: hardcoded values in ~/.gconf

[Tony Houghton <gnome realh co uk>]

In <20030604184701 H26152 devserv devel redhat com>, Havoc Pennington wrote:

> On Fri, May 30, 2003 at 02:59:00PM -0400, John Russell wrote:
> > Herein lies my confusion.  Why is this information necessary?  Why
> > doesn't gconf care at all to whom any particular key belongs? 
> 
> gconf doesn't care - the bugs you've encountered here are application
> bugs, the applications are the ones storing that data.

What about all those muser="..." entries, or don't they matter?

OTOH I'm surprised you go so far as to say these are bugs. Is it wrong
for configurations to no longer apply for a user with a different login
and/or a different home path?

The problem from the programmers' PoV is that you can't feed a filename
beginning with "~", "$HOME", or containing other shell variables, into
any old function and have it work. I'm fairly sure the lower level file
handling functions like the ones in <stdio.h> and <fcntl.h> only work
with expanded paths, and I doubt the GLib functions are any different.
It's theoretically possible to make sure only relative paths are stored
in config, but most things work with absolute paths (eg GTK/Gnome file
selectors), and converting paths, while possible, is extra donkey work. 

-- 
TH * http://www.realh.co.uk