compiz - May 2007 - commit a50d2f9e0f66f445338eb5ad7361b48d48446b29 broke compiz for me

Hello,
as you can see in the other thread the current git does not work for me.
so I did a git bisect and found out that this commit broke it for me:
---------------------
git bisect good
a50d2f9e0f66f445338eb5ad7361b48d48446b29 is first bad commit
commit a50d2f9e0f66f445338eb5ad7361b48d48446b29
Author: David Reveman <davidr at novell.com>
Date:   Fri May 18 16:05:31 2007 -0400

    Remove timeout based iteration of GLib main loop and instead
    require glib plugin.

:040000 040000 b64a5c5fe6207edf7d62e0ed6d45056e4473c2d6 
71b79db9128208721d09f2834b8c23d809776b27 M      metadata
:040000 040000 c2949c4888db71751f697b72e92f60134e85b63c 
0c86ab05232bb33432f499f065a956917e2e6bd9 M      plugins
----------------------

Sam Spilsbury wrote:
> How are you launching compiz? If you are using GConf, then you need to
> launch compiz like this from now on : $ENVIRONMENT_ARGS compiz
> --replace --sm-disable --indirect-rendering glib gconf&
>
If I start it using this command it works. but when I let gnome-session 
start it it doesn't.
but this looks wrong anywhy...
when a plugin depends on some other plugin compiz core should load the 
plugin for it and not rely on the user to do it.

On Sun, 2007-05-27 at 13:02 +0200, dragoran wrote: 
> Sam Spilsbury wrote:
> > How are you launching compiz? If you are using GConf, then you need to
> > launch compiz like this from now on : $ENVIRONMENT_ARGS compiz
> > --replace --sm-disable --indirect-rendering glib gconf&
> >
> If I start it using this command it works. but when I let gnome-session 
> start it it doesn't.
> but this looks wrong anywhy...
> when a plugin depends on some other plugin compiz core should load the 
> plugin for it and not rely on the user to do it.
In a sane system, the user isn't launching compiz manually and launching
compiz with "glib gconf" arguments doesn't look more wrong to me
than
launching it with just the "gconf" argument.

Plugin order is just a metadata detail that the core shouldn't be aware
of. I don't see any good reason for changing that.

-David