Red Hat Bugzilla – Bug 183609
Split Evolution-dependent parts of Beagle into separate package
Last modified: 2007-11-30 17:11:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20060223 Fedora/184.108.40.206-5 Firefox/220.127.116.11
Description of problem:
The latest version of the beagle package depends on evolution-sharp, which depends on evolution itself. Because of this, i have to install NetworkManager, bind, caching-nameserver, dhcdbd and spamassassin as well. I do not wish to turn my workstation into a full-fledged server. I have no use for dns servers, email filter daemons or dhcp stuff other than the client, nor do i wish to use evolution itself.
Therefore, i would like to see the evolution dependent parts split off into a separate package like evolution-beagle or beagle-evolution.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install to beagle
*** Bug 186073 has been marked as a duplicate of this bug. ***
*** Bug 183829 has been marked as a duplicate of this bug. ***
This seems to be because evolution-sharp pulls in a libeshell.so.0 dependency
from evolution, as all other dependencies are from evolution-data-server only. I
wonder what it needs from that.
It seems the only access to eshell is in
Maybe its possible to avoid this? mbarnes, is this possible?
*** Bug 194552 has been marked as a duplicate of this bug. ***
*** Bug 196199 has been marked as a duplicate of this bug. ***
(In reply to comment #4)
> Maybe its possible to avoid this? mbarnes, is this possible?
Any update ?
Verified what alexl found, but have not yet found a resolution to this.
In the course of investigating bug #198191, I discovered that Evolution doesn't
even provide GNOME_Evolution_Shell_findComponent() anymore. It has been
disabled in shell/Evolution-Shell.idl since before Evolution 2.6.
Trying to find out more information about this, but if what I'm seeing is true
then it should certainly be possible to drop the Evolution dependency.
alexl, given the above findings, what do you think is the best course of action?
We can either try to drop the Evolution dependency from Evolution-Sharp
altogether by patching out the already disabled libeshell function, or break the
Evolution-dependent parts of Beagle into a separate package.
One of the upstream guys (varadhan) took a look at this bug and recommended the
latter, although he also commented that he was thinking of dropping the
Evolution dependency from Evolution-Sharp but he needed to talk it over first
with Joe Shaw. So I guess a third option is to wait and see what upstream does.
I talked to joe. They split some beagle backends (like evo) out into a
subpackage. We should probably do that too.
Looks like this is now a beagle issue, rather than evolution-sharp.
Changing component to beagle and reassigning. In the meantime, I'll keep watch
over evolution-sharp's seemingly unnecessary evolution dependency.
This is split out in beagle 0.2.7-8