evo plugin configuration revisited...

["Joseph E. Sacco, PhD" <joseph_sacco comcast net>]

The issue here is how configure handles plugins.  The default is "all".
Configure does attempt to check some of the dependencies for the
plugins. 

As for dbus..., the author of the dbus plugin has been working on a
simple session-dbus-based mail notification applet.  The applet is in
its early stages.


-Joseph


===============================================================================
[Joseph]
(2) desktop/evolution 
The configure process tests for dbus so freedeskstop/dbus might as well
be added to the dependency list. Otherwise, configure will use whatever
it finds. The only way to eliminate looking for dbus is to explicitly
list which plugins are to be built [--enable-plugins = list] 

[Paul]
Why? guenther, can you give me any light as to why an e-Mail client
would need to probe the system bus -- unless we're planning to ship with
libnotify turned on, an inotify-enabled kernel and udev, I can't see why
we'd need it.

Still... if Evo could work on my 'victim' box without trying to eat my
IMAP mailboxes, i'd be really happy.


-- 
joseph_sacco [at] comcast [dot] net