On Mon, 15 Mar 2010 14:31:49 +0100, Patrick Ohly <[email protected]> wrote:
>
> Ove, Frederik, you can continue to use the command line in your
> frontends even when the syncevo-dbus-server is active. We intend to
> change the command line so that it uses the syncevo-dbus-server
> transparently in the final 1.0. Of course, rewriting the frontends to
> use the D-Bus API would be nicer ;-}
>
Does this mean that the syncevolution command line client will depend on
the syncevo-dbus-server (in the sense that it will not function
correctly without it) or just cooperate/offer-more functionality if the
dbus server is available?
I'm curious because right now the ("official") Debian packages split
into two binary packages, one containing the command line client,
another sync-ui+dbus. I think this is worthwhile because the
dependencies of sync-ui are a bit heavy.
I have in an experimental branch also split off syncevo-dbus-server into
its own package, so it would not be much trouble to be more flexible
about what combinations of cli/gtk-client/dbus-server are
installable. We can make sure the default is sensible by using
recommends.
I started thinking about this because the discussion of
syncevo-http-server.py, which I can imagine wanting to have installed
without sync-ui, and which is really a pretty thin wrapper on the dbus
server.
All the best,
David
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
