On Thu, 2008-01-03 at 09:35 -0800, Artem Kachitchkine wrote: > As the one who worked on integrating DBus and HAL into Solaris, I can > tell you that it was my intention to make them both a part of the OS/Net > consolidation, no the Desktop consolidation, since they are both pretty > core OS components. The JDS team, however, insisted that DBus should be > in JDS and, at the time, I did not have the energy to fight another > fight :) Besides, both of those also depend on GLib, and pulling GLib > into ON would be kind of scary - so there wasn't a way we could avoid > ON->Desktop dependency.
Sandwiches are always a problem. Like you said, moving Glib into ON would be the only way to avoid it, but we want to keep Glib updated to the latest and greatest (so we can build the latest and greatest Gtk and the rest of the GNOME stack), so it simply wouldn't work if Glib was in ON. Dbus is not quite as critical, but it's still one of those components that we occasionally need newer versions of and it's a lot easier for us to do that in JDS land than it would be in ON. > With regards to building JDS, I think this is orthogonal to the DBus > issue. Look at how we build ON (OS/Net): building and installing are > distinctly separate phases. We can safely build new OS binaries without > interrupting system operation; we then save our work, log out, load the > new binaries in a matter of minutes (see BFU) and continue using the > system. With JDS, pkgtool will build and install at the same time - and > that can be a problem in some cases. That's the angle you should > approach the issue from, in my opinion. I'm looking at fixing that, or at least giving users the option to build in that fashion. The idea involves a union filesystem and FUSE but it's still in the research phase. When I have anything more concrete, I'll post to desktop-discuss. Laca
