On Fri, 2013-02-01 at 11:24 +0100, Patrick Ohly wrote: > The Evolution UI and camel code in the activesyncd source tree uses it. > I suspect that works (accidentally or intentionally) because it has > access to the internal headers. > > Srini, David, is the libeasmail library supposed to be public or is it > internal to activesyncd?
It's theoretically supposed to be public — although, as you observed, it
has no users outside the activesyncd git tree so it gets away with a lot
of things it shouldn't. Like including other header files that aren't
actually installed outside the activesyncd build tree.
Note it is *part* of the libeasclient library now, not a separate
libeasmail library.
> > eas_mail_handler_get_folder_list works (if I manually copy the parts of the
> > header file that are needed). But I would prefer to use an API exported by
> > libeassync as I don't see listing folders as mail-specific. That would
> > mean
> > adding a new function exported by libeassync and bumping the soname.
In the general case, you don't need to bump the soname for adding a new
function; it doesn't *break* backward-compatibility. You just need to
bump the *minor* number (which doesn't appear in the soname). And list
it with the appropriate version in the symbol version list.
> > Actually, I don't see that the library currently uses sonames -- is that
> > right? It would mean, in any case, that the new syncevolution backend
> > would
> > require the new version of the libeasclient library to build. Any problem
> > with that?
>
> No, fine with me. For the syncevolution.org binaries I am compiling and
> bundling activesyncd.
>
> David, should we start to be more serious about versioning the public
> activesyncd libraries?
Yes, I think that would be a good thing. I'm happy enough to apply the
get_folder_list change that Graham is suggesting, too.
--
Sent with MeeGo's ActiveSync support.
David Woodhouse Open Source Technology Centre
[email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
