[Evolution-hackers] evolution-data-server details

[JP Rosevear <jpr ximian com>]

Ok, so I have a patched evolution locally that uses the
evolution-data-server to obtain its calendar and addressbook data. 
There are two small issues remaining that I'm looking for inspiration on
before committing this all to HEAD:

1. Where to install libical

In evolution we install libical-evolution in privlibdir (and evo
contstruct) rather than the standard $libdir.  For evolution-data-server
the libs are in $libdir - but what about libical-evolution?  Its really
just there because we can't easily mesh with libical releases, so we
don't want it widely used outside evolution-data-server, but its
necessary for now.  So, where to put this?  $libdir I guess and be more
careful about updating the libtool version numbers for this (we'll have
to bump them immediately because for 1.0 or 1.2 I believe we installed
it to $libdir).

2. What to call the backend libraries

The backends were called pas and pcs and name spaced as such.  With the
client libs being libecal and libebook, and all of this being in
evolution-data-server, I named the backend bits libedatabook and
libedatacal.  Obviously, these names need some work.  The main problem
is too have the corba objects in the backend (like the book, the book
view and book factory) not conflict with the client name for the C
wrappers to said objects nor the C classes that do the actual work which
are called by the corba objects (e-book-backend-file, which derives from
e-book-backend).

Any thoughts would be appreciated.

-JP
-- 
JP Rosevear <jpr ximian com>
Ximian, Inc.