$ xclip -o OpenSync 0.38 Release Notes ¶ Yet another E.X.P.E.R.I.M.E.N.T.A.L. release of OpenSync. This release is intended for developers, testers and for packages. OpenSync 0.3x releases aren't intended to be stable. We don't recommend this release for productive use. We don't recommend this release to be packaged as part of a distribution. --- end of sad/scary disclamer --- Late but no too late. We are behind our roadmap again, but the next stable version 0.40 is getting much closer. This release should contain most of all API changes until 0.40. Therefore an invocation to all plugin developers: Please start to port your plugins! Changes since last release: ¶ * Many updates and fixes for the OSyncPluginConfig API o Introduced osync_plugin_advancedoption_get_minsize .. to set minsize and avoid min values e.g. 0 o Added MinSize in plugin_config schema for AdvancedOption o Introduced osync_plugin_connection_set_type() o Introduce initial interface of OSyncPluginConfig "supported" flags. Details: + Purpose of those supported flags are to give the Frontend/UIs information which option are supported by the plugin and should be disabled. This allows to generate "smart" UIs which only show option/fields which are really supported by the plugin at all. For OSyncPluginConnection there are two supported status flags: 1. ConnectionFlags - e.g. USB, Bluetooth, ... to generate bitmask of multiple supported connection types/transports. 2. ConnectionOptionFlags - e.g. RFCommChannel, Port, URL, ... o Added a Preferred element to the Formats. Details: r3659 * Updated example-plugin for current api * Reenabled plain to xmlformat-*-doc conversion * Made osync_assert public. Now plugin developers are able to use osync_assert instead of g_assert or assert. * Packaging with CPack * OpenSync raises an error message if a plugin cannot be loaded * Added sanity check for file-sync. file-sync only supports "file" format, which encapsulates the other formats. * Improved sorting of OSyncXMLFormat fields ( introduced osync_xmlformat_is_sorted(), ...) * Only active OSyncObjTypeSinks for Enabled/Activated Resources: Ticket #817 * Introduced Converter Cache to cache already encountered format converter paths. This should accelerate the conversion. * Syncml-plugin ported to OSyncPluginConfig * Syncml migrated to new high level API of libsyncml (thanks a lot to Michael Bell for his great work on syncml) * New initialize and finalize functions for format plugins to store format plugin related data, e.g. XML schemas. * Plugins which are migrated to 0.38: o file-sync o syncml (requires libsyncml 0.5.0) o google-calendar (beta) o tomboy-sync (beta) o opie-sync (?)
Not sure why a bug was created for this. 0.38 is already in the tree but masked because the plugins need updating. 0.39 also came out today.
Created attachment 204865 [details] osynctool-0.39.ebuild Since the plugins will have to be updated as well, here's an ebuild for the new osynctool, which isn't in the tree yet. I haven't tried to use it yet but it does run. libopensync 0.39 builds fine by just renaming the 0.38 ebuild and removing the Python 2.6 patch. The 0.39 versions of the file, vformat and syncml plugins also build fine. Version 0.36 of the syncml plugin didn't build at all against recent version of libsyncml. The new one successfully builds against 0.5.2 and 0.5.4.
Created attachment 204867 [details] osynctool-0.39.ebuild Sorry, was a little hasty there. It's late. ;)
Please do not mix bump requests with ebuilds requests. Bump is done, re-purposing bug for osynctool request.
this isnt strictly a ebuild request, since osynctool is the new name for msynctool... osynctool is for >=libopensync-0.39 what msynctool was for <=libopensync-0.38 peper: any thoughts? thanks
osynctool seems to work great here. its now available through the bangert overlay. if there are no objections, then i'll add it to portage sometime soon.
app-pda/osynctool-0.39 is now in the tree.
