On Thu, 2008-01-03 at 15:16 +0100, Patrick Ale wrote: > Main reason for this is that in my opinion this is a system package > with system funcionality, far away and outside of the gnome tree.
I think someone already said, we have a lot of "stuff" in JDS that is there because they were needed for the desktop but they are not related to GNOME or the desktop at all. Python is another example. > Little example of first hand experience: > - One does a 'pkgtool uninstall-pkgs *.spec' , per the JDS build instructions. > - One does a 'pkgtool build --download *.spec'. > > Now, asuming you don't run into any problems during compilations you > can't open or close your CD-ROM tray for at least two hours (neither > via the eject command or pressing the buttons on the drive) , until > SUNWdbus is built. Yes, that kinda sucks. We do have this in the build instructions page: "It is advised that you are not logged into GNOME during this step as it uninstalls all GNOME packages. Use a CDE session, remote login or a failsafe session instead". In practice, we build the official JDS builds in chroot jails so we don't have this problem at all. If you have enough disk space you can do that too. > I don't think SUNWdbus is part of GNOME2 under Solaris 10 update4 > either honestly.. No, GNOME 2.6 didn't need dbus. > Isn't it more sense making to move a package that controls hardware to > the system rather than to an optional GUI? Actually, dbus doesn't have anything to do with the hardware, it's just a communications layer. > What if people don't want > to use gnome at all and whipe it from their system to save up > diskspace? They need to keep some of the GNOME libs anyway. glib is one of them, although I'm planning to separate it into its own package but it's not high priority tbh... Laca
