Re: Bug in GARNOME 0.13.1 GConf Makefile (was Gconf won't let GNOME run!)

["James J. Ramsey" <jjramsey_6x9eq42 yahoo com>]

--- Jeff Waugh <jdub perkypants org> wrote:
> <quote who="James J. Ramsey">
> 
> > I don't have /etc/gconf/1/path on my machine, so
> the lines
> > "xml:readonly:/etc/gconf/gconf.xml.mandatory" and
> > "xml:readonly:/etc/gconf/gconf.xml.defaults" get
> appended to
> > $(sysconfdir)/gconf/2/path, where for me
> $sysconfdir is /opt/garnome/etc.
> 
> No - this is for compatibility with system-installed
> GConf 1.x versions, not
> for anything to do with GARNOME or its installation
> directories.
[snip]
> the above system has been in
> place for many, many
> versions of GARNOME (with some changes here and
> there). It is there to
> provide interoperability with the GConf 1.x
> libraries (and thus
> applications, like Galeon).

If the system you discussed has been in place for
several versions of GARNOME, that suggests that there
may have been a change in GConf that broke GARNOME's
system. In any case, GConf *now* certainly refuses to
let GNOME run if $sysconfig/etc/gconf/2/path refers to
files that don't exist. 

Further, whether or not GARNOME'S system worked
before, it is *broken* now. If the files
"/etc/gconf/1/path", "/etc/gconf/gconf.xml.mandatory",
and "/etc/gconf/gconf.xml.defaults" are not on a
system where GARNOME is installed, GARNOME will not
run at all, period. In my book, a bug that prevents
startup is Very Bad(TM).



__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com