[GnomeMeeting-list] what keys does gnomemeeting set through gconf?

[Christopher Marshall <christopherlmarshall yahoo com>]

I have a question about what keys gnomemeeting sets through gconf during the "make install" step.

First, the reason I am asking is that I am having problems building a binary slackware package
from gnomemeeting.

I have two machines running slackware 10.0, kernel 2.4.26.  Let's call them A and B.

I compile gnomemeeting on A and capture it as a binary slackware package.  Everything works fine
on A.

When I install the package on B, however, I get the gconf error when I try to start up
gnomemeeting.

Since slackware packages are (as far as this example is concerned, anyway) straight-forward
gzipped tars, I am essentially doing this:

on A:
./configure --prefix=/usr --sysconfdir=/etc
make
make install DESTDIR=/usr/build
cd /usr/build
tar c . | gzip -c > ../gnomemeeting.tgz
cd /
tar xvzf usr/gnomemeeting.tgz

on B:
(copy gnomemeeting tp /tmp/gnomeeting.tgz)
tar xvzf gnomemeeting.tgz

Then gnomemeeting will work fine on A and hits the gconf problem on B.  I have exactly the same
version of slackware-10.0 installed on A, and B.

Interestingly, the same thing happens if A and B are just different root partitions on the same
machine (I usually setup two independent root partitions on my machines to ease major upgrades).

I have started reading about gconf and I see that it is a registry database of some sort.  So I am
guessing that during the "make install DESTDIR=/usr/build" step, the gnomemeeting build process is
setting keys in my gconf database that have to be available for gnomemeeting to start.  To fix my
binary package I need to know what keys are being set and arrange to set them in an install script
inside the slackware package.

Could someone explain which keys are set and what they mean so I can write a proper install
script?

Chris Marshall