[codehelp <at> debian.org: Status of opensync in Debian - mass removal very likely]

Dear opensync folks,

I guess this may be of interest for you - if you are interested in
keeping opensync in Debian I would ask you to get in contact with the
maintainers (http://packages.qa.debian.org/o/opensync.html).

Kind regards
Harald Jenny

----- Forwarded message from Neil Williams <codehelp <at> debian.org> -----

Date: Sat, 3 Mar 2012 23:15:16 +0000
From: Neil Williams <codehelp <at> debian.org>
To: debian-devel <at> lists.debian.org
Cc: Robert Collins <robertc <at> robertcollins.net>, Michael Banck <mbanck <at> debian.org>, Matthias Jahn
<jahn.matthias <at> freenet.de>, Jonny Lamb <jonny <at> debian.org>
Subject: Status of opensync in Debian - mass removal very likely
X-Local-Spam-Level: 
X-Mailer: Sylpheed 3.2.0beta5 (GTK+ 2.24.10; x86_64-pc-linux-gnu)

opensync/multisync is a complete mess, collecting 25 RC bugs between 20
source packages and a collective 17,626 days waiting to enter testing.
dd-list attached.

Summary:
libopensync-plugin-gnokii	1462 days old (needed 10 days)	libopensync0	RC x 2
libopensync-plugin-gpe		1462 days old (needed 10 days)	libopensync0	RC x 2
libopensync-plugin-irmc		976 days old (needed 10 days)	libopensync0	RC
libopensync-plugin-kdepim	1025 days old (needed 10 days)	libopensync0	RC
libopensync-plugin-moto		1207 days old (needed 10 days)	libopensync0	RC x 2

syncML devel equipment

Hi,

What phone or device is recommended to do syncML development?
All I have are blackberries, and I don't think they support it.

- Chris

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

Q: osync strings glib vs libstd

Hi,
I have a theoretical question rather general as I have been doing a lot of
programming for text processing purposes and always had troubles with
encodings, so I was wondering what should one use when coding for opensync.
There are several advantages when using glib, but also several disadvantages
compared to libstd.

Can you please advise? Or where can I post this question if this is not the
right place for that discussion?

regards

------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/

EBook / ECal new API

Hi,

In helping friends with the last Fedora release, I have noticed that the
ebook / ecal API was modified.

http://www.opensubscriber.com/message/evolution-hackers <at> gnome.org/15214566.html

http://developer.gnome.org/libebook/stable/EBook.html#e-book-free-change-list

We have to worked to adapt opensync evolution2 plugin for the new
Evolution API... Maybe opensync evolution3 plugin :)

Regards,

Nicolas

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

May I modify libwbxml-0.11.0 source code to make it compile, and use it in commercial software

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

_______________________________________________
Opensync-devel mailing list
Opensync-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensync-devel

Cmake Modules repo

http://zi.fi/cmake/Modules/

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

Re: Discussion: syncml plugin with synthesis

Hello Chris,

On Oct 25, 2011, at 10:14 , Chris Frey wrote:

> Thanks... I'm guessing you meant for this to go to the mailing list? 

Yes, sorry. I just sent it again to the list.

> If I wanted to just talk to a SyncML device, get latest changes, get all
> changes, delete records, add/modify changes, and then disconnect, would
> that be possible with libsynthesis?

Unlike many of today's web APIs, a SyncML session has an awful lot of state - you can't use it to just ask for
something in a REST-like manner.

The order of how you have to do the read and write operations is very strict in SyncML. Much in libsynthesis is
about getting this order right, including numerous workarounds for peers that do it wrong. So
libsynthesis has to be in control of the sync session from start to end.

On the DB backend API side, it calls out to plugins to get list of changes, read items, insert/update/delete items.

On the application API side, you can edit the client settings (URL, syncmode etc. - much what you see in a
phone SyncML client, or my iOS apps), then initialize a session, and then "step" through the session. This
means, it's not a single syncNow() function that blocks everything for a long time, but you have your own
main loop which repeatedly calls the SessionStep() API function until the sync is done. SessionStep()
has different return values, and informs you when a SyncML message is ready to be delivered to the peer, or
when a SyncML response is expected from the peer.
So the implementation of transporting messages (via HTTP, BT, whatever) is not in libsynthesis, but must
(can!) be done in the calling code.

Best Regards,

Lukas Zeller, plan44.ch
luz <at> plan44.ch - www.plan44.ch

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning <at> Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev

Discussion: syncml plugin with synthesis

Hi, guys, I'm thinking about writing a plugin that uses the synthesis
engine.
I read about synthesis last year, but I was busy with too many business
stuff to work on something like this.

My proposal is to discuss it here and I'm asking for input basically to work
out the design.
>From the akonadi-plugin experience it is clear what needs to be done on the
opensync side, so I need some ideas how synthesis can be brought into the
game.

I was thinking perhaps to take over the syncml library, but it looks like
there is too much SyncML stuff to care about, which is already done in
synthesis.

If one of you is interested to assist, please let me know.

Your opinion and estimates are really appreciated.

regards

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning <at> Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev

file renames to resolve version conflicts

Hi,

The following commits have been added to the opensync git repo, to resolve
naming conflicts between opensync 0.2x packages and 0.4x packages:

commit 0a1eb5c84b641a02fa75f507844172f9a5d891d9
Author: Chris Frey <cdfrey <at> foursquare.net>
Date:   Thu Oct 20 00:03:33 2011 -0400

    Renamed python module to opensync1, so it can coexist with 0.2x

commit 1f9e2f3852ee206a2fea506d248a0f006bba4659
Author: Chris Frey <cdfrey <at> foursquare.net>
Date:   Wed Oct 19 23:50:45 2011 -0400

    Renamed some internal variables in osync1plugin to match new program name

commit 46825b649f531899b8623aa4050f84692e8da839
Author: Chris Frey <cdfrey <at> foursquare.net>
Date:   Wed Oct 19 23:49:21 2011 -0400

    Renamed tools from osync* to osync1*, so they can coexist with 0.2x

I think this is a good move for python, since the API changed anyway.
And for the tools/ renames, these are mostly debug and development tools
anyway, so I don't see much impact.

Let me know if you think differently.

Thanks,
- Chris

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning <at> Ciosco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev

fixed: evolution syncing problem with get_changes on Debian Squeeze

Hi,

Thought I should post this here as well.  The evolution-data-server
distributed with Debian Squeeze (stable) has a bug in the addressbook
get_changes call, and therefore does not return any changes even if
some were made in evolution.

The patch is available here:

	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641898

I hope that the next point release of Squeeze will have this fixed, as
well as in Ubuntu.

- Chris

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2

Re: [PATCH]: rename plugin set_xxx callbacks to use _func suffix

Merged.  Thanks!

- Chris

On Sat, Aug 27, 2011 at 05:55:19PM -0300, Luiz Angelo Daros de Luca wrote:
> Chris,
> 
> Now I createad all github repos, each project patch and I'm submitting
> the rename again:
> 
> git://github.com/luizluca/opensync-akonadi.git
> git://github.com/luizluca/opensync-barry.git
> git://github.com/luizluca/opensync-evolution2.git
> git://github.com/luizluca/opensync-file-sync.git
> git://github.com/luizluca/opensync-google-calendar.git
> git://github.com/luizluca/opensync-kdepim.git
> git://github.com/luizluca/opensync-luizluca.git
> 
> All using branch rename_plugin_callbacks
> 
> Is it the best way to submit patches?
> 
> Regards,
> 
> ---
> ?? ???? Luiz Angelo Daros de Luca, Me.
> ?? ?? ?? ?? ?? ?? luizluca <at> gmail.com
> 
> 
> 
> 2011/7/3 Luiz Angelo Daros de Luca <luizluca <at> gmail.com>:
> > Hello Chris,
> >
> > I'm back online (back from FISL12). Maybe in the future I can present
> > some stuff about opensync on it 
> >
> > git://github.com/luizluca/opensync-luizluca.git branch rename_plugin_callbacks
> >
> > I also have some other branches on it that I might discuss in the
> > future. I don't know how I could proceed with the plugin's code. The
> > fix on them is trivial.
> >
> > Feel free to comment the patch.
> >
> > Regards,
> >
> > ---
> > ?? ???? Luiz Angelo Daros de Luca, Me.
> > ?? ?? ?? ?? ?? ?? luizluca <at> gmail.com
> >
> >
> >
> > 2011/6/30 Chris Frey <cdfrey <at> foursquare.net>:
> >> Hi Luiz,
> >>
> >> Talk about dropping the ball on this one. ??Sorry about that.
> >> Just getting to this now.
> >>
> >> Unfortunately, the patch is encoded as utf-8, and even when using
> >> utf-8 here, git am complains.
> >>
> >> Seems to be using odd characters on the tabs, or the context lines of
> >> the diff.
> >>
> >> Could you send the patch again, or even better, point me to your git
> >> repo?
> >>
> >> Thanks
> >> - Chris
> >>
> >>
> >>
> >> On Fri, Jun 10, 2011 at 03:10:53AM -0300, Luiz Angelo Daros de Luca wrote:
> >>> Renames the methods that define plugin callbacks:
> >>>
> >>> osync_plugin_set_initialize??->??osync_plugin_set_initialize_func
> >>> osync_plugin_set_finalize??->??osync_plugin_set_finalize_func
> >>> osync_plugin_set_discover??->??osync_plugin_set_discover_func
> >>>
> >>> This makes the callback definition methods similar to the respective
> >>> methods in plugin, format and sink.
> >>>
> >>>
> >>> >From 625b78ba3888ed99235ff71a07e656f4b29d6909 Mon Sep 17 00:00:00 2001
> >>> From: Luiz Angelo Daros de Luca <luizluca <at> gmail.com>
> >>> Date: Wed, 8 Jun 2011 03:34:45 -0300
> >>> Subject: [PATCH 1/1] - Renamed osync_plugin_set_xxx callbacks function
> >>> to use _func suffix
> >>>
> >>> Signed-off-by: Luiz Angelo Daros de Luca <luizluca <at> gmail.com>
> >>> ---
> >>> ??docs/examples/plugins/src/external_demo.c ?? ?? ?? ?? ??| ?? ??6 ++--
> >>> ??docs/examples/plugins/src/plugin.c ?? ?? ?? ?? ?? ?? ?? ?? | ?? ??6 ++--
> >>> ??docs/examples/plugins/src/simple_plugin.c ?? ?? ?? ?? ??| ?? ??6 ++--
> >>> ??.../plugins/src/simple_plugin_static_caps.c ?? ?? ?? ??| ?? ??6 ++--
> >>> ??opensync/plugin/opensync_plugin.c ?? ?? ?? ?? ?? ?? ?? ?? ??| ?? ??6 ++--
> >>> ??opensync/plugin/opensync_plugin.h ?? ?? ?? ?? ?? ?? ?? ?? ??| ?? ??6 ++--
> >>> ??tests/engine-tests/check_engine.c ?? ?? ?? ?? ?? ?? ?? ?? ??| ?? 28 ++++++++++----------
> >>> ??tests/engine-tests/check_engine_error.c ?? ?? ?? ?? ?? ??| ?? ??8 +++---
> >>> ??tests/mock-plugin/mock_sync.c ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??| ?? ??6 ++--
> >>> ??9 files changed, 39 insertions(+), 39 deletions(-)
> >>> diff --git a/docs/examples/plugins/src/external_demo.c
> >>> b/docs/examples/plugins/src/external_demo.c
> >>> index adfbd5e..df59d6d 100644
> >>> --- a/docs/examples/plugins/src/external_demo.c
> >>> +++ b/docs/examples/plugins/src/external_demo.c
> >>> @@ -122,9 +122,9 @@ int main(int argc, char **argv)
> >>> ?? if (!plugin)
> >>> ?? goto error;
> >>>
> >>> - osync_plugin_set_initialize(plugin, initialize);
> >>> - osync_plugin_set_finalize(plugin, finalize);
> >>> - osync_plugin_set_discover(plugin, discover);
> >>> + osync_plugin_set_initialize_func(plugin, initialize);
> >>> + osync_plugin_set_finalize_func(plugin, finalize);
> >>> + osync_plugin_set_discover_func(plugin, discover);
> >>>
> >>>
> >>> ?? /** Client */
> >>> diff --git a/docs/examples/plugins/src/plugin.c
> >>> b/docs/examples/plugins/src/plugin.c
> >>> index eb3edb5..99dcdbf 100644
> >>> --- a/docs/examples/plugins/src/plugin.c
> >>> +++ b/docs/examples/plugins/src/plugin.c
> >>> @@ -402,9 +402,9 @@ osync_bool get_sync_info(OSyncPluginEnv
> >>> *pluginenv, OSyncError **error)
> >>> ?? osync_plugin_set_description(plugin, "A longer description. < 200 chars");
> >>>
> >>> ?? //Now set the function we made earlier
> >>> - osync_plugin_set_initialize(plugin, initialize);
> >>> - osync_plugin_set_finalize(plugin, finalize);
> >>> - osync_plugin_set_discover(plugin, discover);
> >>> + osync_plugin_set_initialize_func(plugin, initialize);
> >>> + osync_plugin_set_finalize_func(plugin, finalize);
> >>> + osync_plugin_set_discover_func(plugin, discover);
> >>>
> >>> ?? if (!osync_plugin_env_register_plugin(pluginenv, plugin, error))
> >>> ?? goto error;
> >>> diff --git a/docs/examples/plugins/src/simple_plugin.c
> >>> b/docs/examples/plugins/src/simple_plugin.c
> >>> index 0b37770..313d859 100644
> >>> --- a/docs/examples/plugins/src/simple_plugin.c
> >>> +++ b/docs/examples/plugins/src/simple_plugin.c
> >>> @@ -322,9 +322,9 @@ osync_bool get_sync_info(OSyncPluginEnv *env,
> >>> OSyncError **error)
> >>> ?? osync_plugin_set_description(plugin, "A longer description. < 200 chars");
> >>>
> >>> ?? //Now set the function we made earlier
> >>> - osync_plugin_set_initialize(plugin, initialize);
> >>> - osync_plugin_set_finalize(plugin, finalize);
> >>> - osync_plugin_set_discover(plugin, discover);
> >>> + osync_plugin_set_initialize_func(plugin, initialize);
> >>> + osync_plugin_set_finalize_func(plugin, finalize);
> >>> + osync_plugin_set_discover_func(plugin, discover);
> >>>
> >>> ?? if (!osync_plugin_env_register_plugin(env, plugin, error))
> >>> ?? goto error;
> >>> diff --git a/docs/examples/plugins/src/simple_plugin_static_caps.c
> >>> b/docs/examples/plugins/src/simple_plugin_static_caps.c
> >>> index c70847d..091fcfc 100644
> >>> --- a/docs/examples/plugins/src/simple_plugin_static_caps.c
> >>> +++ b/docs/examples/plugins/src/simple_plugin_static_caps.c
> >>> @@ -321,9 +321,9 @@ osync_bool get_sync_info(OSyncPluginEnv *env,
> >>> OSyncError **error)
> >>> ?? osync_plugin_set_description(plugin, "A longer description. < 200 chars");
> >>>
> >>> ?? //Now set the function we made earlier
> >>> - osync_plugin_set_initialize(plugin, initialize);
> >>> - osync_plugin_set_finalize(plugin, finalize);
> >>> - osync_plugin_set_discover(plugin, discover);
> >>> + osync_plugin_set_initialize_func(plugin, initialize);
> >>> + osync_plugin_set_finalize_func(plugin, finalize);
> >>> + osync_plugin_set_discover_func(plugin, discover);
> >>>
> >>> ?? if (!osync_plugin_env_register_plugin(env, plugin, error))
> >>> ?? goto error;
> >>> diff --git a/opensync/plugin/opensync_plugin.c
> >>> b/opensync/plugin/opensync_plugin.c
> >>> index b22200d..3afb93a 100644
> >>> --- a/opensync/plugin/opensync_plugin.c
> >>> +++ b/opensync/plugin/opensync_plugin.c
> >>> @@ -165,20 +165,20 @@ void osync_plugin_set_start_type(OSyncPlugin
> >>> *plugin, OSyncStartType start_type)
> >>> ?? plugin->start_type = start_type;
> >>> ??}
> >>>
> >>> -void osync_plugin_set_initialize(OSyncPlugin *plugin, initialize_fn init)
> >>> +void osync_plugin_set_initialize_func(OSyncPlugin *plugin, initialize_fn init)
> >>> ??{
> >>> ?? osync_assert(plugin);
> >>> ?? plugin->initialize = init;
> >>> ??}
> >>>
> >>> -void osync_plugin_set_finalize(OSyncPlugin *plugin, finalize_fn fin)
> >>> +void osync_plugin_set_finalize_func(OSyncPlugin *plugin, finalize_fn fin)
> >>> ??{
> >>> ?? osync_assert(plugin);
> >>>
> >>> ?? plugin->finalize = fin;
> >>> ??}
> >>>
> >>> -void osync_plugin_set_discover(OSyncPlugin *plugin, discover_fn discover)
> >>> +void osync_plugin_set_discover_func(OSyncPlugin *plugin, discover_fn discover)
> >>> ??{
> >>> ?? osync_assert(plugin);
> >>> ?? plugin->discover = discover;
> >>> diff --git a/opensync/plugin/opensync_plugin.h
> >>> b/opensync/plugin/opensync_plugin.h
> >>> index dcfb19e..2ce79e3 100644
> >>> --- a/opensync/plugin/opensync_plugin.h
> >>> +++ b/opensync/plugin/opensync_plugin.h
> >>> @@ -210,7 +210,7 @@ OSYNC_EXPORT void
> >>> osync_plugin_set_description(OSyncPlugin *plugin, const char *
> >>> ?? * @param plugin Pointer to the plugin
> >>> ?? * @param init The initialize function for the plugin
> >>> ?? */
> >>> -OSYNC_EXPORT void osync_plugin_set_initialize(OSyncPlugin *plugin,
> >>> initialize_fn init);
> >>> +OSYNC_EXPORT void osync_plugin_set_initialize_func(OSyncPlugin
> >>> *plugin, initialize_fn init);
> >>>
> >>> ??/** @brief Sets the finalize function for a plugin
> >>> ?? *
> >>> @@ -220,7 +220,7 @@ OSYNC_EXPORT void
> >>> osync_plugin_set_initialize(OSyncPlugin *plugin, initialize_fn
> >>> ?? * @param plugin Pointer to the plugin
> >>> ?? * @param fin The finalize function for the plugin
> >>> ?? */
> >>> -OSYNC_EXPORT void osync_plugin_set_finalize(OSyncPlugin *plugin,
> >>> finalize_fn fin);
> >>> +OSYNC_EXPORT void osync_plugin_set_finalize_func(OSyncPlugin *plugin,
> >>> finalize_fn fin);
> >>>
> >>> ??/** @brief Sets the optional discover function for a plugin
> >>> ?? *
> >>> @@ -234,7 +234,7 @@ OSYNC_EXPORT void
> >>> osync_plugin_set_finalize(OSyncPlugin *plugin, finalize_fn fin
> >>> ?? * @param plugin Pointer to the plugin
> >>> ?? * @param discover The discover function for the plugin
> >>> ?? */
> >>> -OSYNC_EXPORT void osync_plugin_set_discover(OSyncPlugin *plugin,
> >>> discover_fn discover);
> >>> +OSYNC_EXPORT void osync_plugin_set_discover_func(OSyncPlugin *plugin,
> >>> discover_fn discover);
> >>>
> >>>
> >>> ??/** @brief Returns the plugin_info data, set by the plugin
> >>> diff --git a/tests/engine-tests/check_engine.c
> >>> b/tests/engine-tests/check_engine.c
> >>> index b7cb9e5..03bf2e8 100644
> >>> --- a/tests/engine-tests/check_engine.c
> >>> +++ b/tests/engine-tests/check_engine.c
> >>> @@ -289,8 +289,8 @@ static OSyncDebugGroup *_create_group(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> @@ -636,8 +636,8 @@ static OSyncDebugGroup *_create_group2(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize_multi);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize_multi);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize_multi);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize_multi);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> @@ -1037,8 +1037,8 @@ static OSyncDebugGroup *_create_group3(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize_order);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize_order);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize_order);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize_order);
> >>>
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> @@ -1271,8 +1271,8 @@ static OSyncDebugGroup *_create_group4(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize_reuse);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize_reuse);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize_reuse);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize_reuse);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> @@ -1550,8 +1550,8 @@ static OSyncDebugGroup *_create_group5(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize5);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize5);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize5);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize5);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> @@ -1758,8 +1758,8 @@ static OSyncDebugGroup *_create_group6(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize6);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize6);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize6);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize6);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> @@ -1961,8 +1961,8 @@ static OSyncDebugGroup *_create_group7(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize7);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize7);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize7);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize7);
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> ?? fail_unless(debug->client1 != NULL, NULL);
> >>> diff --git a/tests/engine-tests/check_engine_error.c
> >>> b/tests/engine-tests/check_engine_error.c
> >>> index 4eb3f1d..6dd8b40 100644
> >>> --- a/tests/engine-tests/check_engine_error.c
> >>> +++ b/tests/engine-tests/check_engine_error.c
> >>> @@ -210,8 +210,8 @@ static OSyncDebugGroup *_create_group5(char *testbed)
> >>> ?? osync_plugin_set_start_type(debug->plugin, OSYNC_START_TYPE_EXTERNAL);
> >>> ?? osync_plugin_set_config_type(debug->plugin, OSYNC_PLUGIN_NO_CONFIGURATION);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin, initialize_connect_error);
> >>> - osync_plugin_set_finalize(debug->plugin, finalize);
> >>> + osync_plugin_set_initialize_func(debug->plugin, initialize_connect_error);
> >>> + osync_plugin_set_finalize_func(debug->plugin, finalize);
> >>>
> >>>
> >>> ?? debug->plugin2 = osync_plugin_new(&error);
> >>> @@ -223,8 +223,8 @@ static OSyncDebugGroup *_create_group5(char *testbed)
> >>> ?? osync_plugin_set_description(debug->plugin2, "This is a pseudo plugin");
> >>> ?? osync_plugin_set_start_type(debug->plugin2, OSYNC_START_TYPE_EXTERNAL);
> >>>
> >>> - osync_plugin_set_initialize(debug->plugin2, initialize_connect_error);
> >>> - osync_plugin_set_finalize(debug->plugin2, finalize);
> >>> + osync_plugin_set_initialize_func(debug->plugin2, initialize_connect_error);
> >>> + osync_plugin_set_finalize_func(debug->plugin2, finalize);
> >>>
> >>>
> >>> ?? debug->client1 = osync_client_new(&error);
> >>> diff --git a/tests/mock-plugin/mock_sync.c b/tests/mock-plugin/mock_sync.c
> >>> index ecdde36..78f3c32 100644
> >>> --- a/tests/mock-plugin/mock_sync.c
> >>> +++ b/tests/mock-plugin/mock_sync.c
> >>> @@ -794,9 +794,9 @@ osync_bool get_sync_info(OSyncPluginEnv *env,
> >>> OSyncError **error)
> >>> ?? osync_plugin_set_description(plugin, "Plugin to synchronize files on
> >>> the local filesystem for unit tests");
> >>> ?? osync_plugin_set_start_type(plugin, OSYNC_START_TYPE_EXTERNAL);
> >>>
> >>> - osync_plugin_set_initialize(plugin, mock_initialize);
> >>> - osync_plugin_set_finalize(plugin, mock_finalize);
> >>> - osync_plugin_set_discover(plugin, mock_discover);
> >>> + osync_plugin_set_initialize_func(plugin, mock_initialize);
> >>> + osync_plugin_set_finalize_func(plugin, mock_finalize);
> >>> + osync_plugin_set_discover_func(plugin, mock_discover);
> >>>
> >>> ?? if (!osync_plugin_env_register_plugin(env, plugin, error))
> >>> ?? goto error;
> >>> --
> >>> 1.7.4.1
> >>>
> >>> ------------------------------------------------------------------------------
> >>> EditLive Enterprise is the world's most technically advanced content
> >>> authoring tool. Experience the power of Track Changes, Inline Image
> >>> Editing and ensure content is compliant with Accessibility Checking.
> >>> http://p.sf.net/sfu/ephox-dev2dev
> >>> _______________________________________________
> >>> Opensync-devel mailing list
> >>> Opensync-devel <at> lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/opensync-devel
> >>
> >> ------------------------------------------------------------------------------
> >> All of the data generated in your IT infrastructure is seriously valuable.
> >> Why? It contains a definitive record of application performance, security
> >> threats, fraudulent activity, and more. Splunk takes this data and makes
> >> sense of it. IT sense. And common sense.
> >> http://p.sf.net/sfu/splunk-d2d-c2
> >> _______________________________________________
> >> Opensync-devel mailing list
> >> Opensync-devel <at> lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/opensync-devel
> >>
> >

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev