[buteo-syncfw]  fix null pointer crash

stop timer when not needed
Merge pull request #40 from lpotter/master

[buteo-syncfw]  fix null pointer crash
bump version to 0.6.31
[buteo-syncfw] Set ~/.cache permissions correctly

Sets the permissions on the ~/.cache dir in a safe manner
Merge pull request #38 from chriadam/fixonrevert

Fixonrevert
Bump version to 0.6.32
[buteo-syncfw] Add KEY_SYNC_SINCE_DAYS_PAST and KEY_SYNC_ALWAYS_UP_TO_DATE
Merge pull request #44 from nemomobile/past-key

[buteo-syncfw] Add KEY_SYNC_FROM_DAYS_PAST and KEY_SYNC_ALWAYS_UP_TO_DAT...
[buteo-syncfw] Don't rename account profiles when the account display name changes.

The account's profile name is not related to the account's display
name, so changing one should not change the other.
Merge pull request #45 from nemomobile/dont-rename-profiles

[buteo-syncfw] Don't rename account profiles when the account display na...
[msyncd] Use 24 hours as largest BackgroundActivity frequency

Previously, the fallback was the MaximumFrequency value, but this
value is not useful for synchronization schedules.
Merge pull request #46 from chriadam/24h

[msyncd] Use 24 hours as largest BackgroundActivity frequency
Bump version
Created dbus interfaces for base plugin, client and server

The idea of creating out of process plugins is to create separate
processes for each plugin and use dbus to enable communication between
the plugins and msyncd. For this, the main interface methods for Plugins
are converted into dbus interfaces.

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Created OOPPluginManager and the OOPClientPlugin and OOPServerPlugin

The OOPPluginManager is inherited from PluginManager to ensure the
side-by-side compatibality of in-process and out of process plugins.
Also, since the plugins are going to be out of process, the
OOPClientPlugin and OOPServerPlugin are going to act as d-bus interface
interaction instances to deal with the plugin processes. Next, the
methods in PluginManager have to be implemented to start process plugins

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Modified the design. Removed OOPPluginManager

Realised that the PluginManager can handle both the dll plugins and the
OOP plugins. Added two maps for client and server oop plugins. These
maps can be used to keep track of the started/stopped processes

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Added functionality to start, stop a client process plugin

Added functionality in the PluginManager to start and stop process
plugins. Did not want to modify PluginManager to a QObject unless and
until required. So made use of the waitForStarted() and
waitForFinished() methods to block the process startup, shutdown.

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Created OOPClientPlugin and OOPServerPlugin implementation templates

The OOPClientPlugin and OOPServerPlugin instances using dbus to interact
with the process plugins that have been started by PluginManager. All
the signals/slots that are triggered because of the plugins or the
framework are handled by these classes and they inturn
marshall the messages and send them to the process plugins. Similarly,
for the messages received from the process plugins, these classes
unmarshall them and send the appropriate signals

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Created OOPClient and OOPServer plugin objects in PluginManager

The integration of OOP plugin process is complete with the
PluginManager. Now the ClientPluginRunner and ServerPluginRunner will be
able to issue commands to the oop plugins

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>
Created a plugin dbus interface file for client and server plugins

Removed the earlier separate client and server dbus plugin interfaces
and combined them into one dbus interface file. Generated the stubs and
skeleton for the same

Signed-off-by: Sateesh Kavuri <sateesh.kavuri@gmail.com>