Bugzilla – Bug 144606
beagle has too many dependencies
Last modified: 2006-02-02 10:40:38 UTC
beagle has quite a lot of dependencies including: rpm -q --requires beagle mono-core >= 1.1.12 gnome-icon-theme /usr/sbin/groupadd /usr/sbin/useradd mono-web mono-data-sqlite wv gecko-sharp2 gtk-sharp2-complete gmime >= 2.1.16 gsf-sharp >= 0.4 libexif x11-tools mozilla-xulrunner galago-sharp xpdf-tools Does beagle really need all of these dependencies? Especially gtk-sharp2-complete looks like it could be replaced. Since best is not anymore part of beagle, I guess we can remove some dependencies as well - or create some subpackages. For example why is epiphany part of the beagle package and cannot be an optional subpackage?
I'll look into optimizing this. We can drop some of the Requirements with the new release of beagle submitted to autobuild yesterday. gecko-sharp2 mozilla-xulrunner at a minimum.
Joe dropped the galago-sharp dependency. I dropped gnome-icon-theme dependency mozilla-xulrunner The epiphany plugin could be splitout like the firefox plugin, but this doesn't pull in any dependencies. Joe, should we split that subpackage out? Do you have any other ideas for reducing what beagle pulls into a KDE install?
mozilla-xulrunner I think is gone now. We don't need it for anything anymore. The epiphany plugin could be split out, but I don't see any reason to. It's just a build dep, not a package dep. A new version of beagle will further split the UI and non-UI parts, so I think we can move the search UI into a separate package as well, and that'll remove the UI deps from beagled except for gtk-sharp and gtk+.
Joe, are we expecting this near term for SUSE Linux 10.1?
Hoping to do it for Monday.
I checked in the 0.2.1 release which splits up the UI and non-UI elements, and added a beagle-gui package which contains only these bits. The main beagle package still requires gtk-sharp2, but it no longer requires gnome-sharp2 (which in turn would bring in things like the panel, etc.) So I think we can close this as FIXED now.
*** Bug 147568 has been marked as a duplicate of this bug. ***