On Thu, 2006-09-28 at 10:55 -0500, Ian Bicking wrote: > Dan Williams wrote: > > On Thu, 2006-09-28 at 09:49 +0200, Marco Pesenti Gritti wrote: > >> Ian Bicking wrote: > >>> Marco Pesenti Gritti wrote: > >>>> sugar-jhbuild can build python already. The problem is that we still > >>>> depend on some system installed bindings. dbus and avahi that I can > >>>> think of. Both runs a system daemon, so I'm not sure about the best > >>>> way to deal with them. > >>> I was reading in the dbus documentation that even the system-level > >>> daemon can be overridden by an environmental variable. So maybe it is > >>> feasible to build our own dbus? > >> It might be possible. We need to check with J5 when he is back from > >> aKademy. > > > > I think it is quite possible. However, you'd probably need a new system > > dbus config file, if nothing else. But here's the interesting part: how > > does libdbus talk to the system bus? I don't know whether the path to > > the system bus' Unix domain socket is hardcoded in libdbus at build > > time, or what. We can certainly change the location of the system bus > > daemon's socket in system.conf, but I'm unsure how to point libdbus > > there. It's not an environment variable like the session bus AFAIK. > > The docs specifically mentioned that the location of the system bus is > hardcoded, but you can still override it with an environmental variable. > (It didn't mention what that variable was, but this was just in the > tutorial.)
Ok, in that case, we need to build our own D-Bus and our own libdbus, and change the location of the socket. That seems like a really odd road to go down. I don't think we want to start duplicating the entire system inside jhbuild, and system dbus would probably be where I draw the line. That way leads to pain with little benefit :) Dan _______________________________________________ Sugar mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/sugar
